Skip to main content

Audit Trail

The audit trail records every tool call an agent makes. For each call, it records:

  • which tool ran
  • which integration it touched
  • whether it read or wrote
  • what it returned
  • who approved it and why, where a governance policy applied

Find it in a project's Settings → Audit Trail. It shows that project's tool calls.

It covers both kinds of agent: the agents you build in the agent builder (started with autoheal run, a trigger or the Studio), and chat, investigations and alert triage. Calls from all of them appear in one list, newest first.

What a row represents​

One row is one tool call. Approval decisions are not separate rows. They appear as fields on the call they gated.

ColumnWhat it shows
TimeWhen the call was made
ToolThe tool the agent invoked
IntegrationsWhich connected integrations it touched
AccessWhether the call read or wrote. This value is derived from the integration, not guessed from the tool name
ApproversWho approved or rejected, when a policy gated the call
Call summaryA short description of what was requested
StatusThe outcome (see below)
TookDuration
SessionThe agent session the call belongs to. For an agent you built, it opens the run page of the run that made the call

Selecting a row opens a detail pane with the full arguments, the output, and an audit block. The audit block shows the session, the governing policy (linked), and who decided.

Statuses​

The status pill folds several underlying states into plain outcomes.

StatusMeaning
SuccessThe tool ran and returned a usable result
Returned errorThe tool ran to completion, but the target rejected the request. For example: a bad query, an unknown field, or a command exiting non-zero. Not a platform failure
FailedThe call did not complete. It timed out, was blocked, or the model rejected the result and retried
Internal errorA platform or transport fault. The tool never ran, or its result is unreliable
RunningIn flight. The outcome is not known yet
Needs approvalPaused at a governance gate, waiting on a person
Awaiting inputPaused waiting for a human to answer a question
AnsweredA human answered, resolving the call
RejectedA reviewer denied the call. The tool never ran

Two grouping rules are worth knowing when reading the counters:

  • "Returned error" counts toward Success, not Failed. The tool ran and returned a real answer. Only the target's response was negative.
  • The Failed counter covers genuine failures and internal errors, but not rejections. A call a human blocked is its own outcome, not a runtime error.

Filter by integration, status, and time range. The status counters above the table are clickable and act as filter shortcuts.

warning

Search matches the tool name only. It does not search arguments, output, session titles, or user names. A search for a hostname, an IAM role, a repository path, or an error message returns nothing. This is true even when that activity is in the feed. To find a specific call, filter by integration and time range. Then open rows to inspect their contents.

Search is case-insensitive and matches anywhere in the tool name.

Built-in tools are hidden by default​

The Show built-in toggle is off by default. This hides tools that run inside the agent itself. These tools do bookkeeping, such as tracking its task list or recording a hypothesis. They touch none of your systems. Hiding them keeps the feed focused on work that reached your infrastructure.

Anything that resolves to a connected integration is always shown. Sandbox bash is always shown too, because it executes real commands.

note

For agents you build in the agent builder, three built-in tools run inside the agent and are not recorded: update_todos, get_current_time and read_instructions. They do not appear here, even with Show built-in on. They touch none of your systems, and they appear in the run's transcript.

note

While built-ins are hidden, the row counts describe the filtered view. If you are reconciling totals or need a complete record of everything the agent did, enable the toggle first.

Time range and how far back you can look​

The feed opens on the last 7 days. Presets run from the last hour to the last 30 days, and a custom range can be set within that window.

warning

The date picker will not accept dates more than 30 days old. Records older than that still exist. They are simply not reachable from this page. To retrieve them, use the API described below.

Exporting​

Download JSON exports the rows matching your current filters, including the built-in toggle state. The export is capped at 5,000 rows. If your filters match more, you get the most recent 5,000 and a notice that tells you to narrow the range. There is no CSV export.

The same data is available programmatically from the REST endpoint GET /api/v1/runtime/calls. Its old path, GET /api/v1/tools/call, still works but is deprecated and will be removed. The endpoint accepts a signed-in browser session only, not an API credential. The API returns up to 200 rows per request and takes the same filters as the UI. offset + limit must be 5,000 or less; to reach older rows, narrow since and until instead of paging deeper.

Each row has an evidence_id (#ev-<n> or #ev-r<n>) that is unique across all rows; use it, not id, to identify a row. source says which kind of agent made the call: run for an agent you built, agent_session for chat, investigations and alert triage.

Two differences from the page matter:

  • The API has no 30-day limit, so it is the way to reach older records.
  • The API includes built-in tools by default, which is the opposite of the UI. Pass exclude_builtin=true to match what the page shows.

See API Credentials for issuing a token.

Retention​

Tool call records are kept indefinitely. There is no retention period, no automatic expiry, and no purge control. Records are removed only if the agent session that produced them is deleted.

Scope and access​

The feed shows one project's activity for every user. That project is the one open in the project switcher. There is no per-user filter. The narrowest scope available is a single agent session. Viewing it needs tool:read on the project, which Read-only, Member and Project Admin all hold.

warning

Arguments and output are stored unredacted. There is no masking or secret scrubbing. If an agent passes a credential, token, or personal data as a tool argument, the value is stored in full. Anyone who can open this page can see it. Output is stored up to the first 10,000 characters. Treat the audit trail as sensitive. Every role that opens a project, Read-only included, can read its tool calls. So give roles on a project only to people who should see its activity.

See Roles & Permissions for the full permission model and Governance Policies for requiring approval before sensitive calls run.