loading
loading
An append-only record of what the agent did, which tools it called, and who approved each step.
Audit logs turn agent activity into evidence: prompts, tool calls, outputs, approvals, errors, and timestamps. They matter for debugging, compliance, and trust because you can reconstruct why a decision happened instead of relying on memory or screenshots. Example: tracing a bad support reply back to the retrieval result and policy approval that produced it.
Plainly
Think of Audit Log as the checklist that keeps the app open for real people. An append-only record of what the agent did, which tools it called, and who approved each step.
In practice
Use it when a change has to survive deploys, users, incidents, analytics, or billing reality. In practice, define the owner, input, output, and failure mode before you rely on it.