Supported agents
Bring the agent CLI you already use.
Cxddie runs agent CLIs in workspace terminals. You use your own subscription or API key with each provider.
Connected to CAD
These get cxddie-mcp automatically, pointed at the workspace's CAD session.
| Agent | Command | How Cxddie connects it | Install |
|---|---|---|---|
| Claude Code | claude | --mcp-config flag | curl -fsSL https://claude.ai/install.sh | bash |
| Codex | codex | -c mcp_servers.cxddie.* flags | npm install -g @openai/codex |
| GitHub Copilot | copilot | --additional-mcp-config flag | npm install -g @github/copilot |
| Goose | goose session | --with-extension flag | see Goose docs |
| Gemini | gemini | .gemini/settings.json | npm install -g @google/gemini-cli |
| Qwen Code | qwen | .qwen/settings.json | npm install -g @qwen-code/qwen-code@latest |
| Cursor | cursor-agent | .cursor/mcp.json | curl https://cursor.com/install -fsS | bash |
| OpenCode | opencode | opencode.json | npm install -g opencode-ai |
| Droid | droid | .factory/mcp.json | curl -fsSL https://app.factory.ai/cli | sh |
| Kiro | kiro-cli | .kiro/settings/mcp.json | see Kiro docs |
| Charm Crush | crush | .crush.json | brew install charmbracelet/tap/crush |
Project config files are written into the worktree, excluded from git, and never overwrite a file you track yourself.
On Windows, Install uses each agent's PowerShell installer where it has one (Claude Code: irm https://claude.ai/install.ps1 | iex) and npm for npm-based agents. For the rest it opens the agent's homepage.
Agents that accept a starting prompt (all of the above except Kiro, Crush and Goose) can be used with Fan out.
Launch only
These run in workspace terminals but aren't connected to the CAD session (yet): Grok, Amp, Aider, Antigravity, Kilocode, Auggie, Cline, Codebuff, Continue, Kimi, Mistral Vibe, Rovo Dev, Pi, OpenClaude, Trae, Hermes, Devin, Command Code and Autohand Code.
Use cxddie-mcp with any MCP client
cxddie-mcp is a standard stdio MCP server that ships inside the app, as cxddie-mcp.mjs in Cxddie's resources folder. It runs on the Node built into Cxddie, so you don't need Node installed. Point any client at it with the CAD system (freecad, blender, openscad, cadquery, build123d, fusion, rhino) and the port of a running workspace session — or pass --backend and --port:
{
"mcpServers": {
"cxddie": {
"command": "/Applications/Cxddie.app/Contents/MacOS/Cxddie",
"args": ["/Applications/Cxddie.app/Contents/Resources/cxddie-mcp.mjs"],
"env": {
"ELECTRON_RUN_AS_NODE": "1",
"CXDDIE_BACKEND": "freecad",
"CXDDIE_BRIDGE_PORT": "47100"
}
}
}
}On Windows the files are Cxddie.exe and resources\cxddie-mcp.mjs in the install folder (by default %LOCALAPPDATA%\Programs\Cxddie).