Docs / Working with agents

Your agents, coordinated.

Amoeba does not replace your coding agent. It makes the ones your team already runs work as one.

Providers

Claude Code and Codex, side by side.

Every member connects their own CLI under their own login and subscription. Different people can run different providers in the same session.
Amoeba sells coordination, never inference. We dispatch no provider work and pay for no tokens, so there is no markup and no metering.

Onboarding detects the CLIs on your machine and wires up the hooks and coordination tools in one click. A provider we cannot support is shown dimmed with the reason, never silently hidden.

The composer never surprises you.

Every dispatch states its consequence and its payer first: “Prompt your agent. Uses your Claude account.” You choose the intent explicitly; it is never inferred from your wording.
Prompts go to your own agent, in your own lane. Drafts and queued prompts stay per lane.

Steer your own turn. Take over anyone’s, cleanly.

Mid-turn, add guidance to your own running agent: “that endpoint is deprecated, use v2”. Only you can steer your turn, because steering spends your account.
If your turn ends before the guidance lands, the text returns to your composer. It is never silently dropped or billed.

Taking over ends the turn at a safe checkpoint and starts a new turn on your account. The plan, the code and the context carry over, and the agent announces where it resumes: “Resuming at step 8 of 11.”
Two people clicking take over at once resolve to one winner. The other is offered to join instead.

Split off child work without stopping the main lane.

From the composer or a comment, spawn a subagent: an isolated child that runs on your machine and your account, in its own worktree, from an exact snapshot of the session.
The parent lane never pauses. The child streams its progress to the session’s rail.
Only a clean candidate that passes the required checks integrates back, exactly once. A conflict or a failed check leaves the parent untouched and keeps the child’s work reviewable.

Limits and disconnects are planned for, not exceptional.

Hit a usage limit and the session flips to awaiting takeover. A teammate picks it up with full context, and the age of the last synced snapshot is shown before they confirm.
If the coordination server is unreachable, your agent keeps working solo and reconnects on its own. Amoeba fails open; it never blocks your work.
An action interrupted mid-flight (a push, a deploy) is never retried automatically. The record shows exactly what was dispatched and the evidence of what happened, and a person records the outcome.