abadge audit lists the recent audit log for the active organization. Use --json to pipe into jq for structured queries and further filtering.
Usage
Flags
The CLI filter flags map directly to the
GET /v1/audit query parameters. For filtering dimensions the flags don’t cover (surface, field), pipe --json output through jq or call the API directly.
Default output
Pagination
If there are more entries, the CLI printsNext cursor: <value> after the table. Pass it to the next invocation:
Scripting
For structured filtering, pipe JSON intojq:
--result, --agent-id, --item-id, and --event-type filters (see Flags). For the remaining dimensions (surface, field), call the API directly: the GET /v1/audit endpoint accepts all of them.
What audit captures
See Audit log for the full event catalog. Categories includeauth.*, agent.*, permission.*, item.*, profile.*, and access.*.
What audit does not capture
- Secret values
- Encryption material
- Subprocess output from
abadge run