Desktop app · Terminal · MCP
Download Ensemble for your computer.
The desktop app is the easiest start. The ensemble command opens the same Ensemble in your terminal: your tasks, what needs you, and a chat with Claude Code, Codex or Cursor on your own sign-in. Both share one runtime, so install either first.
Desktop app
One download, no setup.
Sign in and it is your Ensemble account in its own window, in sync with the web and your other devices, with this computer running the agent tasks you assign. Or keep everything on this computer: no account, Ensemble's servers never used, your own AI subscriptions and keys. A local-only app can move into an account later, once.
Windows
arm64: .exe installer
Linux
Version 0.8.5. Every build, with checksums, is on the releases page.
First launch
The installers are not code-signed yet. On macOS, open the app once, then choose System Settings → Privacy & Security → Open Anyway. On Windows, SmartScreen shows More info → Run anyway. On Linux, install the .deb, or run chmod +x Ensemble_*.AppImage and start it. Every build, with checksums, is on GitHub Releases under tags starting desktop-v.
Terminal
Install ensemble, then just run it.
Homebrew, Scoop and the scripts install the full terminal app with its own runtime. The npm package only connects editors (MCP).
Homebrew
brew install ensemblework/tap/ensemblebrew uninstall ensembleInstall script
curl -fsSL https://ensemblework.com/install.sh | shensemble runner uninstall
rm -rf ~/.local/share/ensemble-cli ~/.local/bin/ensemblenpm (MCP and login only)
coming soonRequires Node 20+. MCP and login only; no runner.
npm install -g ensemblework
npx -y ensemblework mcpnpm uninstall -g ensembleworkPowerShell
Picks x64 or arm64 to match this computer.
irm https://ensemblework.com/install.ps1 | iexensemble runner uninstall
Remove %LOCALAPPDATA%\Programs\EnsembleScoop
scoop bucket add ensemblework https://github.com/ensemblework/scoop-bucket
scoop install ensemblework/ensemblescoop uninstall ensemblewinget
coming soonComing soon (in review).
winget install EnsembleWork.EnsembleCLIwinget uninstall EnsembleWork.EnsembleCLInpm (MCP and login only)
coming soonRequires Node 20+. MCP and login only; no runner.
npm install -g ensemblework
npx -y ensemblework mcpnpm uninstall -g ensembleworkInstall script
curl -fsSL https://ensemblework.com/install.sh | shensemble runner uninstall
rm -rf ~/.local/share/ensemble-cli ~/.local/bin/ensembleHomebrew on Linux
brew install ensemblework/tap/ensemblebrew uninstall ensembleDebian / Ubuntu
Open the releases page and filter tags starting cli-v.
Download ensemble-cli_<version>_amd64.deb (or arm64) from the latest CLI release
sudo apt install ./ensemble-cli_*_amd64.debsudo apt remove ensemble-cliFedora / RHEL
sudo dnf install ./ensemble-cli-*.x86_64.rpmsudo dnf remove ensemble-cliopenSUSE
sudo zypper install ./ensemble-cli-*.x86_64.rpmsudo zypper remove ensemble-cliArch AUR
coming soonComing soon.
ensemble-cli-binRemove ensemble-cli-bin with your AUR helpernpm (MCP and login only)
coming soonRequires Node 20+. MCP and login only; no runner.
npm install -g ensemblework
npx -y ensemblework mcpnpm uninstall -g ensembleworkManual downloads and checksums
Releases live on GitHub Releases. Filter tags starting cli-v, download the archive or package for your CPU, then verify it against SHA256SUMS.txt.
Use it
Open it in your project. Type / for the rest.
ensemble starts Ensemble on this computer if it is not running, and it keeps running your tasks after you close the terminal. Tasks shows runs and everything that needs you: click an answer, press its number, type your own, or use /allow and /deny. Chat is your agent: Claude Code, Codex or Cursor on your own sign-in, working in this folder under one of your run profiles with your Ensemble board loaded, and remembering the conversation. Or Ensemble Code, with a model key.
◆ Ensemble Tasks · 1 needs you Chat ~/code/shop-api ───────────────────────────────┬──────────────────────────────────────────── NEEDS YOU 1 │ ◆ Fix the flaky checkout test ▸ ◆ Fix the flaky checkout… 2m │ Claude Code · Ask · may commit · sandbox on RUNNING 1 │ ● Add rate limiting 4m │ Claude Code asks: DONE 3 │ Pin the clock with fake timers, or retry ✓ Release notes 1h │ the request twice? 1 ★ Pin the clock 2 Retry twice 3 Skip or type your own answer › Type your answer, or / for commands
cd ~/code/my-repo
ensemble/login
/run fix the failing tests
/profile
/agent
/keys
/runner install/login pairs this computer with your account, so tasks you assign on ensemblework.com or from your phone run here. /runner install starts Ensemble when you log in. For scripts, every command also runs on its own: ensemble help commands.
MCP
Connect your editor with local or hosted MCP.
Local MCP uses ensemble mcp. Hosted MCP uses https://api.ensemblework.com/mcp with header Authorization: Bearer <ens_ key>. Keys come from the Connect page and use the read-only bridge scope.
VS Code
Config file: macOS ~/Library/Application Support/Code/User/mcp.json, Windows %APPDATA%\Code\User\mcp.json, Linux ~/.config/Code/User/mcp.json.
ensemble mcp setup vscode{
"servers": {
"ensemble": {
"type": "stdio",
"command": "ensemble",
"args": [
"mcp"
]
}
}
}{
"servers": {
"ensemble": {
"type": "http",
"url": "https://api.ensemblework.com/mcp",
"headers": {
"Authorization": "Bearer KEY"
}
}
}
}Cursor
Config file: ~/.cursor/mcp.json, or %USERPROFILE%\.cursor\mcp.json on Windows.
ensemble mcp setup cursor{
"mcpServers": {
"ensemble": {
"command": "ensemble",
"args": [
"mcp"
]
}
}
}{
"mcpServers": {
"ensemble": {
"url": "https://api.ensemblework.com/mcp",
"headers": {
"Authorization": "Bearer KEY"
}
}
}
}Windsurf
Config file: ~/.codeium/windsurf/mcp_config.json.
ensemble mcp setup windsurf{
"mcpServers": {
"ensemble": {
"command": "ensemble",
"args": [
"mcp"
]
}
}
}{
"serverUrl": "https://api.ensemblework.com/mcp",
"headers": {
"Authorization": "Bearer KEY"
}
}Claude Desktop
Use the absolute path printed by `ensemble mcp setup --print`, typically /opt/homebrew/bin/ensemble or ~/.local/bin/ensemble.
ensemble mcp setup claude-desktop{
"mcpServers": {
"ensemble": {
"command": "/opt/homebrew/bin/ensemble",
"args": [
"mcp"
]
}
}
}Hosted URL is not supported yet for Claude Desktop custom connectors; they need OAuth. Use the CLI local server.Claude Code
ensemble mcp setup claude-codeclaude mcp add --scope user ensemble -- ensemble mcpclaude mcp add --scope user --transport http ensemble https://api.ensemblework.com/mcp --header "Authorization: Bearer KEY"Codex CLI / IDE
Config file: ~/.codex/config.toml.
ensemble mcp setup codex[mcp_servers.ensemble]
command = "ensemble"
args = ["mcp"]export ENSEMBLE_TOKEN=KEY
[mcp_servers.ensemble]
url = "https://api.ensemblework.com/mcp"
bearer_token_env_var = "ENSEMBLE_TOKEN"Gemini CLI
Config file: ~/.gemini/settings.json.
ensemble mcp setup gemini{
"mcpServers": {
"ensemble": {
"command": "ensemble",
"args": [
"mcp"
]
}
}
}{
"mcpServers": {
"ensemble": {
"httpUrl": "https://api.ensemblework.com/mcp",
"headers": {
"Authorization": "Bearer KEY"
}
}
}
}GitHub Copilot CLI
Config file: ~/.copilot/mcp-config.json.
ensemble mcp setup copilot-cli{
"type": "local",
"command": "ensemble",
"args": [
"mcp"
],
"tools": [
"*"
]
}{
"type": "http",
"url": "https://api.ensemblework.com/mcp",
"headers": {
"Authorization": "Bearer KEY"
},
"tools": [
"*"
]
}Zed
Settings file: macOS/Linux ~/.config/zed/settings.json, Windows %APPDATA%\Zed\settings.json.
ensemble mcp setup zed{
"context_servers": {
"ensemble": {
"source": "custom",
"command": "ensemble",
"args": [
"mcp"
],
"env": {}
}
}
}{
"context_servers": {
"ensemble": {
"source": "custom",
"url": "https://api.ensemblework.com/mcp",
"headers": {
"Authorization": "Bearer KEY"
}
}
}
}Visual Studio 2022 17.14+
Config file: %USERPROFILE%\.mcp.json.
ensemble mcp setup visual-studio{
"servers": {
"ensemble": {
"type": "stdio",
"command": "ensemble",
"args": [
"mcp"
]
}
}
}{
"servers": {
"ensemble": {
"type": "http",
"url": "https://api.ensemblework.com/mcp",
"headers": {
"Authorization": "Bearer KEY"
}
}
}
}JetBrains IDEs
AI Assistant / Junie: Settings → Tools → AI Assistant → Model Context Protocol (MCP) → Add → As JSON.
ensemble mcp setup jetbrains --print{
"mcpServers": {
"ensemble": {
"command": "ensemble",
"args": [
"mcp"
]
}
}
}{
"mcpServers": {
"ensemble": {
"url": "https://api.ensemblework.com/mcp",
"headers": {
"Authorization": "Bearer KEY"
}
}
}
}Cline
MCP Servers → Configure → cline_mcp_settings.json.
ensemble mcp setup cline{
"mcpServers": {
"ensemble": {
"command": "ensemble",
"args": [
"mcp"
],
"disabled": false
}
}
}{
"mcpServers": {
"ensemble": {
"type": "streamableHttp",
"url": "https://api.ensemblework.com/mcp",
"headers": {
"Authorization": "Bearer KEY"
}
}
}
}Continue
Config file: ~/.continue/config.yaml.
ensemble mcp setup continue --printmcpServers:
- name: ensemble
command: ensemble
args: [mcp]mcpServers:
- name: ensemble
type: streamable-http
url: https://api.ensemblework.com/mcp
requestOptions:
headers:
Authorization: Bearer KEYopencode
Config file: ~/.config/opencode/opencode.json.
ensemble mcp setup opencode{
"mcp": {
"ensemble": {
"type": "local",
"command": [
"ensemble",
"mcp"
],
"enabled": true
}
}
}{
"mcp": {
"ensemble": {
"type": "remote",
"url": "https://api.ensemblework.com/mcp",
"headers": {
"Authorization": "Bearer KEY"
}
}
}
}Qwen Code
Config file: ~/.qwen/settings.json.
ensemble mcp setup qwen{
"mcpServers": {
"ensemble": {
"command": "ensemble",
"args": [
"mcp"
]
}
}
}{
"mcpServers": {
"ensemble": {
"httpUrl": "https://api.ensemblework.com/mcp",
"headers": {
"Authorization": "Bearer KEY"
}
}
}
}Kimi Code
Config file: ~/.kimi-code/mcp.json.
ensemble mcp setup kimi{
"mcpServers": {
"ensemble": {
"command": "ensemble",
"args": [
"mcp"
]
}
}
}{
"mcpServers": {
"ensemble": {
"url": "https://api.ensemblework.com/mcp",
"headers": {
"Authorization": "Bearer KEY"
}
}
}
}Mistral Vibe
ensemble mcp setup vibevibe mcp add ensemble --transport stdio --command ensemble --arg=mcpvibe mcp add ensemble --url https://api.ensemblework.com/mcp --transport streamable-http --header "Authorization=Bearer KEY"FAQ
Requirements and security.
What systems are supported?
macOS 13+ on Apple Silicon or Intel, Windows 10/11 x64 or arm64, and Linux x64 or arm64 with glibc 2.35+ (Ubuntu 22.04+, Debian 12+, Fedora 36+). Git is needed for code tasks. The terminal app is about 120 MB because it carries its own Node runtime and local database.
Where do keys live?
Model keys you add with /keys or in the desktop app stay encrypted on your computer and are never sent to Ensemble. Claude Code, Codex and Cursor use their own sign-in. The ens_ key the CLI or the Connect page creates reads your Ensemble context, and makes changes only if you allowed that when you made it.
Is there a sandbox? Do I need Docker?
No Docker, no VM. Commands run in the operating system's own sandbox: Seatbelt on macOS, bubblewrap or Landlock on Linux, and a separate sandbox account on Windows (set up once, with one Windows permission prompt). Writes stay in the task's folder, your keys and browser data stay unreadable, and the internet is off unless the task allows it.
Where can tasks run?
In the folder you opened ensemble in, or a fresh clone of a repo, inside the sandbox. Tasks from the web run only in folders you share with this computer. /logout removes this computer from your account.
Will macOS or Windows warn about unsigned builds?
The desktop installers do, once (see First launch above). The terminal app does not when installed with Homebrew, Scoop, the install scripts or the Linux packages; a zip you download by hand may need “Open anyway” or “Run anyway” once.
Desktop app or terminal?
Either, or both. They share one runtime on a computer: one database, one pairing, one list of trusted folders, one sandbox. A task started in one shows up in the other, and either can answer what it asks.