Show HN: Stroq – a local audit of what your coding agent did and why
Why CEREBRO kept it
Audits coding agent actions; directly on-topic, local tooling.
The text below is an automated extraction of the article at https://github.com/AGGIB/Stroq, stored verbatim in the public cerebro-vault repository. Copyright remains with the original publisher (github.com).
Stroq reads your own Claude Code and Codex sessions and shows how many commands came from text your agent read, and which keys left your machine. An example: a made-up machine with made-up sessions, keys and hosts. Hoo is Stroq's owl. Your card shows your own sessions. npx @stroq/cli It reads your last 30 days of sessions, your key files and the folders your agent worked in; prints key names, never values; writes nothing but a small cache under ~/.stroq; and sends nothing. No account, no telemetry. npx @stroq/cli a card of your own sessions, like the one above npx @stroq/cli init
Community take
Commenters say an eBPF backend would cover far more adversarial cases than a local command audit, and that dev work should run in a VM regardless.
Who builds this
AGGIB is profiled here from public GitHub push activity.
Backlinks
Appeared in 1 briefing