How Amoeba separates parallel agent changes with Git worktrees
What Git worktrees separate, what local agent processes can still reach, and what to review before integrating parallel AI coding work.
Amoeba can place a joined session or local subagent in a dedicated Git worktree. The task gets its own working directory and checked-out HEAD while the main checkout’s working tree remains unchanged. A session-specific branch handles cases where Git will not check out the same branch twice.
This separates working-tree changes. It does not create a container, network boundary, or separate operating-system identity. Agent commands still run locally under the current user and can reach resources allowed by the provider’s permission or sandbox mode.
Before integration, review the diff, run the repository’s checks, and consider shared services, credentials, caches, ports, Git objects, and remote systems. Removing a worktree is cleanup, not proof that every side effect was undone.
Amoeba also stores coordination records and encrypted transcript chunks in the Brain. Worktree separation does not imply zero data retention.