Audit & traceability

Chronos records everything that matters, so you can always answer who did what, when, and against which checks. Traceability isn’t an add-on — it’s built into how the platform works, end to end.

What’s recorded

• Every instruction given to an agent.
• Every change a session produces.
• Every command run and tool used.
• Every approval, pull request and merge — with the person who did it.
• Capabilities turned on, off, or installed.

Two complementary trails

• Daemon audit (local). Sessions, prompts, tool calls, commands, approvals — the full story of the work itself, recorded by the daemon.
• Panel audit (cloud). Governance actions with their actor: who authorized or revoked an MCP, credential mints (which server, by whom), cascade and role changes, and which sessions loaded which catalog version. Administrators review it in the dashboard’s Audit tab.

The panel audit complements the daemon audit; neither replaces the other.

Trustworthy by design

• Append-only. Entries can’t be edited or deleted after the fact. That’s what makes the record dependable as evidence.
• No secrets, ever. The audit notes that a tool was used and by whom — never the credential. A mint entry records which server was minted, not the token; a governed prompt’s change entry records metadata only, never the markdown body. Values are redacted before anything is written to logs or the store.
• Complete. From the first instruction to the final merge, the whole story is captured — including failures, such as a context bundle rejected for an invalid signature.

Why it matters

• Compliance & review — reconstruct exactly what happened on your codebase.
• Accountability — every approval and merge carries its owner and the checks it passed.
• Confidence — proof that agents stayed within your organization’s rules and never had access to your secrets.

Administrators review governance activity centrally in the panel — see the Administrator guide.