Skip to content
Docs · Rules, answers, steps and expiry

DocsHow it works

Rules, answers, steps and expiry

Rules

Rules are the orders you give every agent, like “use pnpm, never npm”. Every agent gets them at the start of each session, first, before any other memory. People add and edit them on the Rules page; an agent can only propose one (propose_rule), and it waits there until a person accepts it. Every change is kept in the rule's history and can be brought back.

arcroom import turns the rules you already wrote (CLAUDE.md, AGENTS.md, Cursor rules) into cards on the Rules page. When an imported file changes on your main branch, the change comes back as a card to accept. Rules an agent already reads from its own file are not sent to it twice.

For each finished task ArcRoom can keep two things: the answer, and the steps that produced it. They are reused differently.

Answers

The result itself, for example the list of breaking changes in a release. An answer is handed over as it is while it is fresh. By default that is 1 day. An owner can set anywhere from 1 hour to 30 days under keep answers for. When your agent saves an answer, it can give it its own lifetime instead, up to a year (for example a few hours for prices). Each time a teammate's agent is handed the answer for the same task, that lifetime starts again, but never runs past a year from that moment. A hand-over for a similar task does not count toward used and does not renew it. Once an answer expires, its steps are still handed over and the agent redoes the work. A pinned version is handed over even after it expires. An answer about your code is tied to the files it depends on and is reused only while those files are unchanged.

Workflows

How the work was done: the files it changed, the files it needed, and the check that proved it. Steps are kept after the answer expires, and handed over so the next agent can follow them instead of exploring again. ArcRoom records code changes from the session itself, so the agent doesn't save them by hand.

A task with side effects (a deploy, a migration, a code change) is never reused as a result. Only its steps are handed over.

At the end of a job the agent writes a Task: line naming the job and a Card: line saying what it did. The same job asked again, in the same or close words, starts with its steps. A big job is split into parts one level at a time: at most 8 parts, and never more than 5 levels deep. The agent gets one level, each part with its id, and opens a part made of its own parts only when it starts it. A part another job could use is kept as a workflow anyone can reuse; a part that only fits its own job is kept for that job alone and never offered to others. A part that broke is redone from the step that failed. Steps followed and parts reused are counted as reused work on the dashboard.

Versions

Every save is a new version, with who saved it and whether it passed its checks. Steps that fail when followed fall back to the last good version. A version can be pinned for a branch or for yourself.

Decisions

Save a team decision with why you made it and what it beat. A newer decision on the same choice retires the older one, so agents are only handed the current one.

arcroom decide "Weekly report goes out Monday" --why "clients read it at the start of the week" --over "Friday, Sunday"

Memory is grouped into desks, one per project or area. arcroom init --desk sends a folder's saves and lookups to its desk, and on the Memory page you can rename, merge or archive a desk, or move a memory to another one.

Removing or retiring memory

  • arcroom wrong [reason] reports the memory your agent was just handed. If that hand-over had several, the command lists them and you name one: arcroom wrong <memo id>. One report takes effect at once: a wrong answer is thrown away, broken steps fall back to their last good version, and a wrong decision stops being handed over. Once two different people on the team have reported the same memory, it is deleted for the whole team and cannot be restored. Reporting it twice yourself still counts as one report.
  • Expire or remove a memory on the Memory page in the app.
  • Expiry limits let an owner stop old answers from being handed over (set with arcroom rule):
    • --idle-days 30: skip an answer nobody has reused for 30 days.
    • --max-hits 50: skip an answer once it has been reused 50 times.
    • --tag prices: apply the limit only to answers your agent tagged prices (tags are set when the agent saves the answer). Without --tag, the limit covers every answer.
    There is one limit per tag, and setting it again replaces it. arcroom rule with no limits (or only --tag) removes it. Only workspace owners can set limits. These are not your agent rules from CLAUDE.md or AGENTS.md. Nothing is deleted: the steps are still handed over, the agent redoes the work and saves a fresh answer, and a pinned version is still handed over.

How “tokens saved” is estimated

Estimated tokens saved is what the reused work cost the first time: the tokens spent making an answer or steps, counted each time they are reused. The small context ArcRoom adds to hand it over is not subtracted.