Per-Task Project Memory That Never Creates a Merge Conflict
Each task's agent now writes its own memory file instead of sharing one document with every other task, so finishing work no longer conflicts with other work.
Summary
Effigate Command Center's project memory has been redesigned so that each task's agent writes its own dedicated memory file, rather than every task sharing and editing the same document. That one change removes a reliability problem where multiple pieces of work in progress at once could end up conflicting with each other purely because they were trying to update the same shared file.
What You Gain
Previously, every agent run added its own notes to one shared project memory document, which meant any two pieces of work in progress at the same time were liable to edit the exact same lines of that document. Merging one piece of work could instantly create a conflict in another unrelated piece of work still in progress, simply because both happened to update their notes in the same place — occasionally backing up your whole review queue over something that had nothing to do with the actual code being reviewed.
Now, your project's main memory document keeps only the stable, big-picture information — your project's overview, structure, and conventions — while each task writes its own dedicated memory file as part of its own work. Two tasks never touch the same file, so this entire category of conflict is gone. Because each task's memory travels with its own change, canceling or reverting a task now also cleanly removes its memory entry, and a fresh look at your project only ever reflects the history of work that actually went through.
Once a task's work is merged, its memory becomes part of your project's record automatically, shown newest first, so your project's accumulated knowledge is always a clear, readable log of what actually shipped.
How It Works
- Your project's main memory document now holds only stable, high-level information: overview, structure, features, and conventions.
- Each task writes its own dedicated memory entry as part of its own work, so two tasks in progress at once never conflict.
- Once a task's work merges, its memory entry is automatically folded into your project's record, newest first.
- Canceling or reverting a task cleanly removes its memory entry along with it.
- This requires your project's GitHub connection to have read access to your repository's contents; without it, a simpler activity note is used instead.
Where to Find It
Find your project's accumulated memory on its Brain tab. Existing projects are already using the new structure — there's nothing you need to set up, beyond making sure your GitHub connection has read access if you want the full merged view.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.