Stroq audits coding-agent sessions and guards the next one

Stroq is an open-source local tool for Claude Code, Codex, Cursor and similar agents. It reads the last 30 days of sessions on your machine, flags commands that came from text the agent read, and checks whether known keys left the machine (names only, never values). There is no account and no telemetry. `stroq init` installs hooks that can deny curl-to-shell and outbound calls carrying known secrets, and ask before a command repeats suspect text. `stroq attack` replays 36 known attacks in a sandbox; on 0.30.0 the project says 0 of 36 passed through. HN (90 points, 34 comments): No consensus. One camp says auditing is too late and you need a sandbox or isolated user instead. Another says audit logs are needed to keep access policies honest over time. The author clarifies that init hooks prompt before risky commands, and that Stroq is a filter, not a sandbox. Sorted take: run the secret scan and hooks, but still isolate the agent; do not treat rules alone as a containment boundary.