Docs / Code and Git
Git stays the source of truth.
Amoeba rides on top of git and GitHub. It never replaces them, and your code never leaves your machines.
Your repo, your credentials, your rules.
The contract
- 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.
Sessions cannot trample your checkout.
Isolation
- Joining a session materializes it in a dedicated git worktree. Your main checkout is untouched, several sessions coexist on one machine, and a dirty tree never blocks a join.
- Switch branches manually inside a session worktree and the session pauses with a banner instead of corrupting anything. Resume when you are ready.
A real editor with your agent in the bottom panel.
Two modes
- 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.
See the diff while it is being made.
Live review
- 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.
Two machines, one branch, no clobbering.
Snapshots
- 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.