We build Chron, a tool that records AI coding sessions locally so there is an audit trail of what an agent actually did. It passed 12,000 downloads recently. The records are hash chained, they live on your own machine, and nothing is sent anywhere on its own.
The principle has not moved since the first release: Chron records what happened. It does not certify that what happened was correct.
Which means the interesting failures are not in what we record. They are in what we do not.
The problem with asking a model to log
Chron's primary capture path is an MCP server. The agent calls log_message , Chron writes a row, the row joins a hash chain. This works.
It works when the model calls the tool.
When it does not, you get a perfectly good answer from the agent and no record of it. Nothing in the database distinguishes that from a tool that was never installed, or one that failed silently, or a server that was configured but never attached.…