How to connect Claude Code, Codex, Gemini CLI and other agents to Tallos

How do agent connections work in Tallos?

Connections is the Settings page where Tallos installs agent CLIs and signs you in to them. Each AI coding agent is a separate program from its maker. Tallos does not bundle or resell model access: it uses the subscription or API key you already have with Anthropic, OpenAI, Google and the others, and runs each agent in your workspaces.

Every card shows the agent's version and one of four states: Not installed, Installed, not signed in, Installed, sign-in unknown (the vendor offers no reliable way to check) and Connected. The buttons change with the state: Install, Sign in, Use API key, Models and Docs.

How do I connect an agent to Tallos, step by step?

1. 1

   Open Settings → Connections

   Open Settings and choose Connections. Tallos checks which agent CLIs are on this computer and shows a card for each supported one. Click Refresh after installing anything outside Tallos.

2. 2

   Install the agent

   Click Install. Tallos shows the vendor's official install command and runs it only after you confirm, streaming the output. If the card says Needs Node.js first or Needs Homebrew first, install that tool and click Refresh. When no verified one-click install exists, Open install guide takes you to the vendor's docs.

3. 3

   Sign in with your account

   Click Sign in. Tallos opens the agent's own login command in a terminal, for example claude auth login or codex login, and you finish it in the browser as usual. Sign-in needs an open project; without one, run the command in any terminal.

4. 4

   Or use an API key

   For agents that accept one, click Use API key, paste the key and click Save key. Tallos confirms with API key saved in secure storage and never shows the key again. Remove saved key deletes it.

5. 5

   Check the models

   Expand Models to see what the agent offers. Tallos lists models reported by the tool itself when it can, otherwise a known catalog, and says so on the list.

6. 6

   Set your default agent

   Open Settings → Agents and choose the Default Agent. New workspaces preselect it. You can also click Set as default in the agent selector when creating a workspace.

Bring the agents you already pay for. Get Tallos and connect them in one place.

Get Tallos →

How does each agent install and sign in?

Every install command, login command and environment variable Tallos uses comes from the vendor's official docs or repository. On Windows, all one-click installs use npm; on macOS, Tallos prefers Homebrew where the vendor documents it.

Other agents, such as GitHub Copilot CLI, still run in Tallos from the agent picker. They do not have a Connections card, so install and sign in with the vendor's own instructions; Tallos picks the CLI up once it is on your PATH.

Where does Tallos store my API keys?

Tallos stores API keys in your computer's secure storage (the keychain on macOS, the system's protected storage on Windows) and never displays them again. When Tallos starts an agent, it injects that agent's saved key as the vendor's documented environment variable, and only into that agent's process. Claude Code's key never reaches Gemini CLI, and the other way round.

• Environment-variable agents (Claude Code, Gemini CLI, Grok CLI): Tallos keeps the key and passes it at launch.
• Codex: Tallos passes the key once to codex login --with-api-key, Codex saves it in its own settings, and Tallos keeps no copy.
• OpenCode, Qwen Code, MiMo Code: keys are managed inside the tool itself, so Use API key is not offered.
• Remote workspaces: saved keys are host-local and are not sent to SSH hosts.
• No secure storage available: Tallos refuses to save the key rather than storing it in plain text.

How do I switch my default agent?

Change the default under Settings → Agents → Default Agent, or click Set as default next to any agent in the New workspace dialog. The default is only a preselection: you can still pick any installed agent per workspace, run several Claude Code sessions in parallel, or mix agents inside a squad.

Troubleshooting: why does an agent show as not connected?

• Installed but Tallos says Not installed. The CLI is not on the PATH Tallos sees. Restart Tallos after installing, then click Refresh.
• Sign in does nothing. Open a project first; the login runs in a terminal inside it. Or run the login command in any terminal and click Refresh.
• Installed, sign-in unknown. Some CLIs have no status command. Start the agent once; if it works, you are signed in.
• The tool rejected the key. Paste it again without spaces, and check it is a key for that vendor.
• The install timed out or failed. Read the output in the install dialog. Network, proxy or npm permission problems are the usual causes; the vendor's guide has manual steps.

Try it on your own repo.

Get Tallos →