Check exactly what was sent
Cost, safety and controlSecurity-minded team lead
Before rolling ArcRoom out, the lead wanted to see what actually leaves a laptop.
How can I audit exactly what an AI agent tool sends from a developer's laptop?
Run arcroom sent to see what ArcRoom sent, or arcroom sent --all to see it exactly as sent, for example arcroom sent 2026-10-31 --all. Every event passes through a local spool on the way out, and what was sent is kept on the laptop for 7 days. Older history is only in the API.
Also asked as: Before rolling out an agent tool, how do I see what actually leaves our laptops? · How do I see what my AI agents send? · Can I get a log of every event an agent plugin sent?
Every event passes through a local spool on the way out.
- Redaction
$ arcroom sent 2026-10-31 --all
Step by step
- Every event passes through a local spool on the way out.
- What was sent is kept for 7 days.
- arcroom sent shows it, and arcroom sent --all shows it exactly as sent.
What the agent sees
$ arcroom sent 2026-10-31 --all
142 events · 0 file contents · 3 [secret file] redactionsCompared with today's tools
A local proxy (e.g. mitmproxy)
The lead routes agent traffic through a proxy on one laptop and inspects what the memory tool sends.
- Setup
- 1–2 hours
- Ongoing
- manual inspection each time, ~30 min
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 sent)
- Ongoing
- None
A proxy is an independent check and so a stronger one; arcroom sent is quicker to read but is ArcRoom reporting on itself.
Where it stops
Kept 7 days on the laptop. Older history is only in the API.
Try it in your project
Works with the agents your team already uses, and any agent over MCP or the HTTP API.