Code and Git

Repositories

01

Your repo, your credentials, your rules.

A workspace wraps a repository you already have: point Amoeba at your local clone during setup.
Code moves over plain git under your own credentials. Amoeba’s server coordinates metadata (sessions, plans, presence, memory) and never holds your source.

02

Dedicated worktrees separate session changes from the main checkout.

Amoeba can materialize joined sessions and subagents in dedicated Git worktrees. Each gets its own working directory and checked-out HEAD; a session branch is used when Git cannot check out the same branch twice.
A worktree is not a container or security boundary. Commands run locally under your user account and can still reach shared credentials, services, caches and networks allowed by the provider’s permission mode.
Switch branches manually inside a session worktree and the session pauses with a banner instead of corrupting anything. Resume when you are ready.

03

A real editor with your agent in the bottom panel.

Amoeba is a full desktop editor. Your agent lives in the bottom panel: a native conversation surface, or the CLI’s own terminal, unfiltered.
Terminal mode passes every byte through. Your CLI’s own controls, like Shift+Tab for permission modes, keep working exactly as they do outside Amoeba.

04

See the diff while it is being made.

Watch changes land live in any lane, and comment on the exact range or hunk.
When an agent wants a gated action (a push, a network call, an external command), an approval card names the exact action, the files touched and who is asking. Any editor can answer, and the first valid response wins.

05

Two machines, one branch, no clobbering.

A session’s branch syncs continuously between participants’ machines as snapshots, checked three ways before they apply.
A conflict keeps both versions and shows a “2 versions” chip so people compare and pick. There is no silent overwrite.
Finishing is ordinary git: commits and a pull request. Merging completes the session.