Solutions
How do I give coding agents shared memory between sessions?
Updated
Write it down once, in a notebook the job can reach, and the next agent starts already knowing it. In Forkbench each job has a Thread — its own plan, its own notes, its own keys — so a note filed there outlives the session that wrote it, and any agent you open in that Thread reads it on arrival.
You spend the first ten minutes of every session re-explaining the same things. Which package manager. Why that module is the way it is. What was already tried and did not work. Close the pane and it goes; open a second agent alongside the first and it starts from nothing while the first one already knows. The usual fix is a markdown file at the root of the repo, which works until you have three of them, or until the work spans two repositories, or until the agent that needed the context was the one you opened somewhere else.
The difference from a CLAUDE.md or an AGENTS.md is what the memory is attached to. A file in a repository belongs to that repository and to whichever agent has learned to read that filename, so it does not follow the work across two repos and it does not carry to the next agent you install. A note granted to a Thread belongs to the job. Any agent working in that Thread can list it, read it and write to it through the same interface, whether it is Claude Code, Codex, Cursor, Gemini CLI or Antigravity CLI, so the thing a Codex session worked out at midnight is what a Claude Code session opens at nine. Agents write back too, which is the part that compounds: the plan, the decisions and the dead ends accumulate as the work proceeds rather than being reconstructed each morning. Notes are sealed on your Mac before they are stored, so what makes them portable between your agents does not make them readable by us.
How it works
- 1Make a Thread for the job rather than for the repository, so the memory follows the work and not the folder.
- 2Write the standing facts into a notebook once: the conventions, the decisions, what has already been ruled out.
- 3Grant that notebook to the Thread. Nothing is visible to an agent until you grant it, so an agent working elsewhere cannot read it.
- 4Tell the agent to file what it learns as it goes, so the next session inherits the work instead of the summary.
- 5Open a second agent, from any vendor, in the same Thread. It reads the same notes without being told anything.
Straight about the guarantee: Notebooks are free, unlimited and synced across your Macs on every plan; per-note version history and the cross-notebook library are the Pro side. And a note is only as good as what goes in it — an agent that is not told to write things down will not, so the instruction to file findings belongs in the Thread's own notes.