Skip to content
Docs · How recall works

DocsHow it works

How recall works

Each time you send a prompt, ArcRoom asks your workspace whether this task, or one like it, was done before. On a hit, it hands the agent what was found before it starts. The agent doesn't call a tool or need to remember to ask, so there is no extra prompt.

What can be handed over

  • A team answer, reused as it is while it hasn't expired.
  • Steps from a past session: the files it changed, the files it needed for that, and the check that proved it.
  • Steps that broke: when the stored steps failed last time, the agent is told, with the last failure, so it plans around them instead of trying them again.
  • A playbook: the shared pattern of three or more similar sessions that passed their checks.
  • Team decisions that match the request, newest first.
  • The code map: who is editing nearby, and which folders changed.

Everything found shares one small budget, most useful first, and nothing already handed over in the session is repeated. When nothing matches, the agent gets a short note about ArcRoom's memory tools instead.

The code map

The code map tells your agent who is working on the folders a request touches, and what teammates changed there, before it starts work. It is on for every git repo you set up with ArcRoom.

What it holds for each repo:

  • The repo's shape: folder and file paths and their git hashes, read from git. Not file contents. Your default branch sends its whole tree once, then only what changed. Other branches send only what differs.
  • Who is editing what: when your agent edits a file, the file, branch, agent and your name (the part of your email before @) are shared for about 10 minutes. Another agent that is about to edit the same file is warned first.

Everyone in your workspace gets the code map through their agents.

CommandWhat it does
arcroom codeshows how many folders and files ArcRoom has for this repo and how many agents are editing it now
arcroom code syncsends the repo’s tree now instead of at the next session
arcroom code offstops the code map for this repo. Commit .arcroom.json so your whole team gets the same setting
arcroom code onturns it back on

Turning it off stops new uploads. What was already sent stays until you delete the project.

How a match is found

The first 300 characters of your prompt are sent for the lookup. Tasks are matched on their wording and on their meaning. Meaning comes from Google's Vertex AI embedding model (gemini-embedding-001), which the ArcRoom API sends that text to. A similar task is offered only above a set similarity, and the hand-over says when it is similar rather than the same.

Provenance

Handed-over steps say their version, whether they passed their checks, how often they were followed since, when and by whom they were saved, and whether they come from a branch that is not merged yet. An answer says whether its author marked it verified.

What teammates' agents wrote is handed to your agent marked as reference material from teammates, not as instructions. Steps are checked against your checkout first: renamed files are followed, deleted ones dropped, changed ones flagged, and steps whose files are mostly gone are skipped.

When a session starts

The agent starts with your team's rules, then a short note on what the last session in this project did, which may be a teammate's or another agent's.

When the first ask is a job the playbook has split before, the known parts come back first, so the agent doesn't plan it again.

If a hand-over was wrong

Run arcroom wrong, with a reason if you like. See Answers, steps and expiry for what happens next.

By agent

Claude Code and Codex get the hand-over with the prompt. Cursor gets it with the first tool call of the turn. OpenCode gets it in that turn's system prompt (experimental). See Agent support.