I built a little "police department" for my Claude Code subagents
Summary
A logging hook and CLI tool that records all tool calls and permission events from Claude Code agents into a session log, then replays the log to audit for misbehavior like unauthorized file reads or permission escalation. It is a catch-and-report flight recorder, not a blocker.
Similar Articles
Show HN: A police department for your Claude Code agents
agent-pd is an open-source logging and monitoring tool for Claude Code agents that records all tool and permission events and replays them through deterministic detectors to catch rule violations, without blocking any actions.
I kept reading “Claude Code deleted my X” threads, so I built a check that runs before each action: is this the job?
A solo developer introduces Watchdog (alovia-watchdog), a deterministic, fail-closed per-action guard that checks every agent tool call against a one-line mission statement, reporting 0 harmful calls across promptfoo and AgentDojo red-team runs with low latency.
I built a prototype that turns Claude's raw SSE stream into a forensic timeline of tool calls and file diffs.
A developer built a prototype that intercepts Claude's raw SSE stream from the web interface, parsing the JSON into a forensic 'Case Bundle' dashboard that reconstructs tool calls, links failures to their causes, and displays code diffs for verifying fixes — all without using the official API.
We built a self serve security report triage agent with Claude Code.
A demo of a self-serve security report triage agent built with Claude Code, which reads emails, accesses source code in a sandbox, and emails a suggested response to the user.
My Claude Code agent ran for 40 minutes while I got coffee. I have no idea what it actually did.
A user describes running Claude Code agent unsupervised for a refactor task, expressing concerns about the lack of visibility into its actions and calling for better monitoring in AI development tools.