Use Claude Code or Codex in one shared AI IDE
How teammates connect supported local agent CLIs, share coordination context in Amoeba, and recover when a provider or coordination is unavailable.
Supported agent CLIs
Amoeba supports Claude Code and Codex. Each teammate runs a supported CLI on their own machine under their own provider login. Different teammates can use different supported providers in the same shared workspace.
Amoeba does not bundle a model or resell provider tokens. The selected CLI sends prompts and required code context to its provider under that account’s data controls. The Brain also processes prompt-derived coordination context for session summaries and overlap checks, including processing by Anthropic.
Before you start
- Install Amoeba for your platform.
- Open the local Git clone you want to use and sign in with GitHub.
- Install Claude Code or Codex and be ready to sign in to that provider.
- Have an Amoeba workspace connected to the local clone. If your installation does not offer a way to connect one, ask the teammate who invited you or your Amoeba administrator before continuing.
Connect a provider
- Open Welcome or Setup and continue with GitHub.
- Review the disclosure explaining what runs locally and what workspace data is shared with the Brain.
- Choose Claude Code or Codex. Amoeba checks whether that CLI is installed.
- If sign-in is required, use the provider sign-in action in Setup. The provider’s local CLI handles authentication.
- Select the workspace connected to your local clone.
- Choose “Set it up for me” to install the adapter and coordination tools.
- Start the guided first session or open Mission Control. Repeat provider setup on each teammate’s machine.
Limits and recovery
Repository content is synchronized through Git using the configured remote and the user’s Git credentials. The Brain does not store a repository copy. Provider CLIs still send the prompt and code context they need to their model services.
- Provider not detected: install the supported CLI, complete its sign-in, reopen Setup, and run detection again.
- Workspace unavailable: confirm that this machine has a local clone connected to the workspace, or ask the teammate who invited you or your administrator.
- Coordination offline: the agent continues solo and reconnects automatically. Overlap warnings may be missing or use stale cached context.
- Another provider appears: treat it as unsupported unless Setup explicitly marks it available. Gemini can appear as unavailable.
Install and complete first setupProvider setup and recoveryWork in a shared session