Troubleshooting
First run arcroom doctor in the project folder: it checks your key, the API, the setup in this folder and the background uploader, and tells you how to fix each problem.
Nothing shows up in Memory or Usage
Run arcroom whoami to check the key and workspace. Run arcroom on in case the repo was switched off. If doctor finds nothing, look at these files: events waiting to be sent are in ~/.arcroom/spool.jsonl, and the uploader writes what went wrong to ~/.arcroom/daemon.log.
Codex records nothing
Trust the project in Codex, then approve ArcRoom once with Codex's /hooks command.
Cursor gets the memory late
That is how Cursor works: it can't add context to a prompt, so the hand-over comes with the first tool call.
OpenCode never recalls anything
Run npx arcroom init --agent opencode again to update the setup, then restart OpenCode. Recall uses an experimental OpenCode feature, so a newer OpenCode may have changed it.
“done-checks … not asked for: read them with arcroom checks”
The checks in .arcroom.json are new or changed. Read them with arcroom checks, then run arcroom checks approve <code> in your own terminal (it refuses inside an agent).
“memory offline, prompt sent without it”
The API didn't answer within 3 seconds. Your prompt went on without memory; lookups pause for a minute.
“skipped stored steps: their files are not in this checkout”
The steps found were about files your checkout doesn't have. Nothing was handed over.
A hand-over was wrong
Run arcroom wrong with a reason. To report an older one, pass its id from the Memory page: arcroom wrong <id> <reason>.
ArcRoom stopped working on one laptop
Its key was probably revoked or its account removed. Run npx arcroom init with a new key.
I need it off right now
arcroom off in the repo. Nothing from it is recorded or sent from this laptop until arcroom on.
Still stuck? Write to sachin.kumar@arcroomai.com, or use Help & support in the app when signed in. Security reports go to the same address.