Fail-open behaviour
If ArcRoom fails, your agent carries on without it: memory lookup gives up after 3 seconds and the prompt goes through.
On your laptop
- Any error inside ArcRoom lets the agent's call through. ArcRoom always exits cleanly.
- Recall waits at most 3 seconds. If the API is slow or down, the prompt goes on without memory and you see
memory offline, prompt sent without it. For the next minute, prompts skip the lookup so an outage costs that wait once, not on every prompt. - If the last session's note can't be fetched when a session starts, the session starts without it.
Uploads
Events go to a local queue (~/.arcroom/spool.jsonl) first, and the uploader sends them when it can. Offline or with the API down, nothing waits: events stay in the queue and are sent when you're back online.
When ArcRoom does stop the agent
Only in three cases, all on purpose:
- Loop guard: the third identical tool call in a row is blocked.
- Done-checks: if your approved checks haven't passed since the agent's last edit, it is asked to run them before it stops. It is sent back at most twice, then let go and the session is marked partial.
- Same file: if another agent is already editing a file, your agent's first edit to it is held back once and told who is on it. If your agent makes the edit again, it goes through. If ArcRoom can't check in time, the edit goes through.
A revoked key
If ArcRoom refuses a laptop's key, ArcRoom does nothing at all on that laptop until npx arcroom init is run with a new key.