Audit log
Every agent confirmation that got an answer, with the source that decided it — you, a rule, the autonomy level or the deny-list — so you can find and fix whatever let an agent act on its own.
The Audit tab is the answer to “why did the agent just do that?” Every moment an agent confirmation received a response — from you or automatically — is one row.
Columns
| Column | Meaning |
|---|---|
| Time | When it happened |
| Project | Which project |
| Agent | Which session |
| Action | What the agent was asking to do |
| Decision | Approved or refused |
| Source | What made the decision |
| Keystroke | What was actually sent to the CLI |
Reading the source column
| Source | What it means |
|---|---|
| You | A human answered from the queue |
| Manual injection | You sent a specific choice yourself |
| Auto rule | One of your rules matched |
| Broad level | The extended autonomy level approved a simple confirmation |
| Human level | The strictest level routed it to you |
| Deny-list | The built-in hard deny-list refused it |
When something happened that you did not expect, this column names the culprit in one glance: an over-broad prefix rule, or an autonomy level set higher than you remembered.
What it does not do
The audit traces decisions; it does not undo the disk effects an agent already produced. The app is explicit about this rather than implying a rollback that does not exist.
What it gives you is the loop that actually prevents a repeat: find the row, read the source, open Rules, narrow or disable the rule that matched.
Where it lives
An append-only file in the config directory. Local, like everything else — see Telemetry & privacy.
The blind spot worth knowing
The audit can only record confirmations that existed. A CLI launched with its dangerous flag — Skip all permissions, Bypass approvals + sandbox, Yolo — never asks anything, so its actions produce no rows at all. That is not a gap in the log; it is what those flags mean. See Agent settings.
Frequently asked
- Can the audit log undo what an agent did?
- No. It records decisions, not disk state. Its job is to let you understand what allowed an action and disable the faulty rule; reverting the files themselves is your version control's job.
- What does the source column tell me?
- Who answered — you, a manual injection, an auto rule, the broad or human autonomy level, the hard deny-list, or the engine dispatching or parking a session.