Switch it off for one sensitive repo
Cost, safety and controlTeam with one repo under NDA
One client contract forbids any external service touching their repo.
How do I turn off an AI agent memory tool for one repo under NDA?
Run arcroom off in that repo to stop ArcRoom there on this laptop, including anything still queued. Other repos keep their memory. Run arcroom on to turn it back on. It's per laptop, so each developer has to turn it off.
Also asked as: A client contract says no outside service can touch their repo. What do we do with agent tools? · How do I turn ArcRoom off for one repository? · Can I keep agent memory on for most repos but off for one?
arcroom off stops ArcRoom for that repo on this laptop, including anything still queued.
- Off switch
$ arcroom off
Step by step
- arcroom off stops ArcRoom for that repo on this laptop, including anything still queued.
- Other repos keep their memory.
- arcroom on turns it back on.
What the agent sees
$ arcroom off
ArcRoom is off for this repo. Queued events for it were dropped.Compared with today's tools
Leave the tool out of that repo
Developers don't add the memory tool's MCP server or rules to the NDA repo.
- Setup
- 5 min
- Ongoing
- check each developer's setup by hand
ArcRoom
Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.
- Setup
- built in (arcroom off)
- Ongoing
- None
Same result for a tool set up per repo; arcroom off also drops events already queued and works even after arcroom init --everywhere.
Where it stops
It's per laptop. Each developer has to turn it off.
Try it in your project
Works with the agents your team already uses, and any agent over MCP or the HTTP API.