How to export audit and compliance data
Reconstruct any run step by step from the append-only audit log, and export it for your regulator.
Every agent action lands in an append-only audit log designed for 7-year retention — the regulatory minimum for the vertical — configurable per tenant.
What you can reconstruct
For any past run: the exact Catalog version the agent executed (recorded as a Git SHA), the model used, the ordered tool calls with their inputs and outputs, token usage, cost, and duration. With the V1 Beta, human approvals and denials join the log as first-class entries with who, when, and why.
Who sees what
Workspace admins review audit entries in the Console; compliance roles export them as CSV for regulators and internal audit; incident responders query them when something needs investigating.
Beta
The audit-log viewer UI is rolling out with the V1 Beta. Audit capture itself is live today — entries are written from the first run, so history is complete when the viewer lands.
Traces complement the log
Operational traces — every model and tool call with latency and cost — live in the observability stack and deep-link from each run, complementing the compliance-grade audit log.
Still stuck?
Tell us what you were trying to do and where it failed — screenshots and run IDs help. A human follows up.