Agents & terminals

Every workspace opens with the agent you chose. + Terminal adds another agent or a plain shell, all rooted in the workspace's worktree.

For CAD-connected agents, Cxddie hands the agent cxddie-mcp, pointed at the workspace's CAD session. Nothing to configure:

• Claude Code, Codex, Copilot, Goose receive it through command-line flags.
• Gemini, Qwen Code, Cursor, OpenCode, Droid, Kiro, Crush read a project config file Cxddie writes into the worktree (for example .gemini/settings.json). That file is git-excluded, and Cxddie never overwrites one you track yourself.

Other agents launch in the same terminals without CAD tools — useful for code, docs or scripts next to the model.

Terminals use your login shell on macOS and Linux, and PowerShell on Windows (PowerShell 7 when it's installed).

After a restartCopy Anchor Link

Cxddie remembers each workspace's terminals. When you open the workspace again they come back, and agents pick up their conversation: Claude Code resumes the exact session Cxddie started it with, and Codex, Gemini, Copilot, Cursor, OpenCode, Droid and Goose resume their latest session in the worktree. Other agents and shells start fresh. Closing a tab forgets it.

Dropping filesCopy Anchor Link

Drop files on an agent's terminal to paste their paths into the prompt, escaped the way your system's terminal writes them, so agents that understand dropped paths (such as Claude Code with images) pick them up. An image dragged from a web page has no path, so Cxddie saves it to the workspace's .cxddie/attachments first.

Plan usageCopy Anchor Link

The status bar along the bottom shows how much of your Claude Code and Codex plan you've used: one chip per agent with its fullest limit and the time until it resets. Click a chip for the Usage panel, with your plan, the 5-hour and weekly limits, and a refresh button. The agent in the active terminal is listed first.

Cxddie reads the logins the CLIs already store and never refreshes or changes them.

TipsCopy Anchor Link

• Run a shell next to the agent for git log, git diff and quick checks.
• Two agents in one workspace share the same CAD session. That's handy for review ("check what the other agent built"), but for competing attempts use Fan out.