Skip to content

Audit ​

There are two independent logs: Tara's log and the Guardrails log on your machine. This page explains what each log records, who can read it, and how secrets are masked.

Tara's log ​

For each important change, Tara writes a record in the same transaction as the change. So if a change succeeded, a record exists. The log covers five groups of events: review (approve, return with a reason), version lifecycle (release, deprecate, yank), roles (grant and revoke), reports (suspicious resources and how they were handled), and notification channels (create, edit, and delete an organization's channels). Each record states who did it, when, on which resource, in which organization, and the reason if there is one.

View the log ​

On the Portal, open your organization's settings and choose Audit log. With Phillip, use the ph tara audit command.

bash
ph tara audit --since 7d
ph tara audit --action version.yank --org acme
ph tara audit --actor <login> --resource <resource-name> --limit 50 --json
OptionMeaning
--since, --untilTime range, such as 7d or 2026-10-01
--actorThe person who acted
--actionExactly one event, or a whole group such as version
--resource, --orgFilter by resource or organization
--limit, --jsonNumber of records, machine-readable format

Results are paginated, newest first.

Who can read the log? ​

Owners and Admins of an organization see that organization's events, and nobody sees another organization's log. The log opens only through a sign-in session, and an API token can't read it.

How are secrets masked? ​

The log doesn't expose secrets. A reason typed by hand has strings that look like tokens, keys, or passwords masked, both when it's written and when it's read, and only a predefined list of detail keys is displayed. Even so, don't paste sensitive information into the reason field.

The Guardrails log on your machine ​

The Guardrails hook server writes each decision (block, ask, mask, record) to a JSONL file on your machine. On macOS, the file is at ~/Library/Application Support/AI-Forge/audit.jsonl and rotates when it reaches 50 MB.

Each record has the time, the event, the session ID, the directory, the branch, the task ID, the decision, the IDs of the rules that decided, the waived rules, the policy in effect, and the masked content. Content is masked with every masking rule in the policy, so the original secret isn't in the file. If no policy has been loaded, the content isn't saved, because there are no rules yet to mask it.

You can view your own log with these two commands.

bash
ph guardrails audit --days 7
ph guardrails audit --rule <rule-id> --samples 5

The second command shows masked context samples around the times a rule matched, which is handy when you suspect a rule blocked by mistake. Then you send feedback with ph guardrails feedback.

What goes to Ryoma ​

Each Guardrails decision also creates a metadata-only event, sent to Ryoma through the telemetry path. The event has the rule ID, decision, severity, policy, session, repo, task ID, and tool name, with no content. If Ryoma hasn't received it yet, Phillip keeps the event in memory, with a limit, and sends it again later.

Ryoma's Collector records only some of these fields. See Data collected for exactly which fields are stored.

The detailed audit store is off by default ​

Ryoma can keep a detailed, masked audit store for Security. The store has a retention period, and only Owners and Admins can read it. It is off by default at both ends: the user's machine must be installed with the option to send audit, and Ryoma must turn on receiving. Turn it on only after the legal department approves the scope of what's recorded. If your Owner or Admin hasn't announced that it's on, the Guardrails log stays only on your machine.

Next steps ​