Skip to content
Docs · Done-checks

DocsHow it works

Done-checks

Done-checks are the commands that prove a change works. They keep an agent from saying it's done while they still fail.

Add them

In the repo's top folder, in .arcroom.json. They hold in every subfolder and git worktree of the repo:

{ "doneChecks": ["pnpm -s test"] }

Approve them

They are shell commands from the repo, so each person reads and approves them once per repo on their laptop. Nothing is asked for until then.

arcroom checks                  # shows the commands and a code
arcroom checks approve <code>   # approves exactly those commands

The code belongs to the exact commands shown. If .arcroom.json changes (a pull request, a teammate, an agent's edit), the checks stop being asked for until you approve them again. Approval works only in your own terminal, not through an agent.

In CI there is no terminal: set ARCROOM_APPROVE_CHECKS to the code in the job's environment, and run arcroom flush as the last step so what is queued is sent before the job ends.

What happens

  • When a session starts, the agent is told your done-checks, so it can run them right the first time.
  • When a turn that edited files is about to stop, ArcRoom checks whether your approved checks passed since the last edit.
  • If not, it asks the agent to run them with its own shell tool (Bash, or PowerShell on Windows). ArcRoom never runs them itself, so every run goes through your agent's permission prompt.
  • A check counts as passed when the agent ran it and it succeeded after the last edit.
  • The agent is sent back at most twice. After that it is let go, and the session is marked partial instead of done.

In Cursor the request arrives as a follow-up message; in OpenCode it runs when the session goes idle.