Supported agents
Connecto runs agent CLIs through adapters: one per tool. Two are available, and three are next.
| Agent | Status | Command for a new terminal |
|---|---|---|
| Claude Code | available | connecto add claude · ⌘ ⌥ 1 |
| Codex | available | connecto add codex · ⌘ ⌥ 2 |
| Plain shell (not an agent) | available | connecto add shell · ⌘ ⌥ 3 |
| Gemini CLI | next | |
| Cursor CLI | next | |
| opencode | next |
Available today
Claude Code and Codex both have everything in these docs: terminals, the connecto command, automations, packages, isolated and system profiles, history, and remote sessions.
- Connecto does not pin a CLI version. It relies on the tools staying compatible, and runs its own verified copy, made from your install at the first launch. To pick up a newer version by hand, run
connecto-app provision. - The tools' own auto-update is turned off inside Connecto, so a session never changes under you.
- Writing a new package with an agent's help uses Claude. Titles use Claude too.
A plain shell
Besides the agents, a terminal can be your login shell: $SHELL started as an interactive login shell in the project folder, so it has the environment you know. It has no turns, no login and no launch mode, so its dot is a small grey square that only says it is running. Other terminals drive it with connecto send <id> '<one command line>' and connecto read <id>; --ask and watch are refused, because a shell has no end of turn to report. It is held to the same rules as any terminal: Pause blocks writes, and every write is in the audit log. It is also as powerful as a bypass-permissions agent, so treat access to it that way.
Next: Gemini CLI, Cursor CLI and opencode
These three are being built now. This page will list what each supports as it lands.
The aim is for a new agent to be a full member of the workspace, not a second-class terminal:
- its own terminals, in the same project tree, with the same states;
- the
connectocommand, so it can ask Claude or Codex for help, and be asked; - the same Pause, audit log and redaction;
- a place in packages, automations and per-project settings, as far as each tool allows.
How far each one goes depends on what the CLI itself offers: for example, whether it reports the end of a turn, and whether it can resume a conversation.
What an adapter does
For each tool, an adapter tells Connecto how to:
- launch it, with which options and which profile folder;
- sign in, and tell whether it is signed in;
- know when it is ready for input, when a turn starts and when it ends;
- capture its reply, so
send --askcan deliver it; - resume a conversation from the history.
Adapters are part of Connecto itself. A new agent arrives with a new version of the app.