Two AI agents need one live memory file

Problem

Parallel AI coding feels magical until both agents start maintaining their own version of reality.

One agent remembers a rule from chat history. The other reads a repo note that is already stale. A workflow gets updated in one place but not the other. The user ends up repeating the same instruction twice, forwarding approvals manually, and cleaning up collisions that should never have happened.

In practice, the user becomes the synchronization layer.

Real cause

The root problem is not "bad memory." It is multiple writable memory surfaces.

If one agent treats a handoff file as live state, another agent treats a different file as live state, and both also rely on thread memory, the system has no clear authority. Drift is guaranteed.

The same thing happens with parallel edits:

• no single place to check whether another lane is active
• no explicit ownership boundary
• no habit of writing what changed, why, and what not to touch

The agents are not just missing information. They are missing a shared contract about where truth lives.

Why this takes longer than it should

This failure mode is subtle because each individual step feels reasonable.

• documenting in two places feels safer
• asking the user to confirm again feels polite
• starting work before checking for another active lane feels fast

But those local optimizations create a global tax:

• duplicated instructions
• overwritten edits
• ambiguous approvals
• no usable history when something breaks later

The system looks collaborative on the surface while quietly depending on the user to keep it coherent.

The operating model that fixes it

Use one mutable collaboration-memory file and make everything else point to it.

Then add four rules:

1. Current truth has one home.
   One live file holds active rules, ownership, open lanes, and recent decisions.

2. History is preserved, not silently deleted.
   Resolved rollout history moves to an archive file so future debugging can reconstruct what changed and why.

3. Cross-agent review is direct.
   If one agent needs the other's approval, use a direct review/delegation mechanism instead of making the user relay the same context twice.

4. Parallel work starts with a pre-flight check.
   Before meaningful edits, check for active lanes, declare ownership, and define a do-not-touch boundary if overlap is possible.

A simple template that works

Keep a tiny Active Work block in the live memory file:

- owner: Codex
- scope: admin workflow cleanup
- started: 2026-04-29 08:30 Vienna
- do-not-touch: app/admin/* until handoff

That one block turns "I thought nobody was in there" into an avoidable mistake instead of an excuse.

Reusable rule

If multiple AI agents touch the same codebase, the collaboration system is part of the product.

Do not optimize only for generation quality or coding speed. Optimize for:

• one live memory source
• explicit temporary ownership
• direct agent-to-agent review
• traceable history

Otherwise the user will end up doing project management by hand while the agents appear autonomous.

That is not automation. It is outsourced coordination.