Audit on tokening.net

Exporting One AI Agent Session for a Reviewer to Check

Sat, 31 Oct 2026 00:00:00 +0000

A reviewer wants to see what one agent did during a session. They shouldn’t get the whole database, which holds every agent’s history and the encrypted credentials. They also shouldn’t have to take a hand-made summary on trust. What they need is that agent’s slice of the log, in a file they can check on their own laptop.

This run used the same session as the publish replay case study, recorded on Tokening 0.1.4 with a stand-in CMS on the same machine. The agent in question is editor-bot. It had a two-use grant to fix a typo in the title of post 3, and a second grant for post 4 that the operator revoked before it was used. All commands and output are in the case study folder, including the exported file itself.

Flight Recorder Recipes for Audits and Incident Reviews

Sat, 31 Oct 2026 00:00:00 +0000

The flight recorder needs no setup. It starts writing the moment Tokening 0.1.2 or later opens your database. What it does need is a few habits around it. Here are the ones we’d start with.

Every command below was run against the database from our case studies, on Tokening 0.1.4, and the output shown is copied from the recorded runs. Paths are examples. All flight commands open the database read-only, so they’re safe next to a running server.

Replaying an AI Agent Publish Session With the Tokening Flight Recorder

Sat, 31 Oct 2026 00:00:00 +0000

An agent was given one job: publish post 7, the launch note someone had already approved. It got a grant for exactly that. One call to publish_post, bound to id 7, valid for 15 minutes. Afterwards we wanted to know what it actually did, in order, without asking the agent.

This is a real run, recorded on Tokening 0.1.4. The upstream was a small stand-in CMS that speaks MCP over HTTP, running on the same machine, so nothing touched a real site. The script, the policy and every line of output are in the case study folder of the code repo, and you can run it again yourself.

Tokening Adds a Flight Recorder for AI Agent Actions

Sat, 31 Oct 2026 00:00:00 +0000

A grant says what an agent may do. After the task, you want to know what it actually did, and you want a record that can’t be quietly tidied up afterwards. Version 0.1.2 adds that record.

Tokening now writes every grant, every call the agent makes, every decision and every upstream result into an append-only log. Each entry carries the SHA-256 hash of the entry before it. Change one, delete one, swap two or cut the end off, and the chain breaks at that spot. tokening flight verify tells you which entry and why.

When Someone Edits the Audit Log Behind an AI Agent

Sat, 31 Oct 2026 00:00:00 +0000

Picture the morning after. An agent had a grant to publish post 7, and on the way it tried post 8. The refusal sits in the log as entries 2 and 3. Someone with access to the server would rather that attempt wasn’t there. Maybe they set the agent up and the attempt looks bad. They open the database with sqlite3.

We ran that incident for real, on copies of the database from the publish session case study. Tokening 0.1.4, a stand-in CMS on the same machine, every command and its output saved in the case study folder of the code repo. The original log had 20 entries.