How Amoeba warns when AI coding work overlaps
A practical guide to overlap warnings, advisory file locks, team coordination choices, and the cases where agents can continue without a warning.
Why parallel agents still collide
When two people send AI coding agents into the same repository, both agents can choose the same file or solve adjacent parts of the same task. Git can expose the conflict later, but by then both agents may have produced changes that need to be untangled. Amoeba adds an earlier coordination check to the shared workspace.
The check helps people decide who should continue. It does not prove that an edit is safe, and it does not stop a local process from writing a file.
What Amoeba compares
Before a connected agent runs a prompt, its local hook asks the Brain for coordination context. Exact same-file activity is reported as overlapping. Related planned work or task descriptions can be reported as adjacent.
- The current branch and files open in active sessions.
- File paths named in active plans.
- Task titles, task summaries, and the new prompt description.
- Teammate and session context for any possible overlap.
How to respond to a warning
- Open the named session in Mission Control and check its task, branch, active files, and latest plan.
- If both agents are solving the same problem, join that session or let its current owner continue.
- If the work can be split, assign non-overlapping files or plan steps and state the split in the session.
- Before editing, have the agent acquire advisory locks for the exact file paths it owns. Treat a held path as a request to coordinate.
- Review both diffs before integration. A clean warning state does not replace Git review or tests.
Limits and troubleshooting
The prompt hook waits briefly for the local daemon. If the daemon or Brain cannot answer, the hook exits successfully so the agent can keep working. It may return cached coordination context or no context. Warnings also depend on accurate paths and task descriptions from connected agents.
File locks are atomic for an open file path inside a session, but they are advisory. They are not a cross-workspace filesystem barrier, and they do not pause another local process. Amoeba can reduce silent duplication when coordination is healthy; it cannot guarantee zero duplicated work or zero wasted tokens.
- No warning appeared: confirm that the provider adapter is installed, the local connector is running, and the agent is connected to the intended workspace.
- The warning looks stale: open Mission Control and ask the named teammate before editing.
- Two agents changed the same file: stop new edits, compare both diffs, choose one owner, and move the other task to a separate file, plan step, or worktree.
Coordinate live sessionsSeparate changes with Git worktreesProvider setup and recovery