StackMap
Subscribe
Explore / Tracekit
Cygnux-Labs

Tracekit

Flight recorder for AI agents: policy-gates every tool call before it runs, holds risky ones for human approval, and signs each action into a tamper-evident log anyone can verify offline.

734 130 Python MITupdated today
View on GitHubDispute this mapping →
Curator's take

Use it when agents touch real systems and you must prove to customers or auditors what happened — the signer sits outside the agent's reach, so a compromised agent can't rewrite history. `tracekit audit --since 7d` over your Claude Code logs is a zero-install way to see what it would have caught. Overkill for local tinkering; it gates and records, it doesn't sandbox — pair with real isolation for untrusted code.

Mapped by ShipWithAI editors · links verified

Continue your stack

What teams reach for next — and why each earns a place beside Tracekit. Ranked by curator confidence.

pairs wellpairs wellpairs wellalternativealternativepipelockOpenShellOrcaReplayfailproofaiagentsightTracekit
pairs wellalternativebuilt withpick a node for the why · open it from the panel
Weekly digest
README.md2 min read

Tracekit: the tamper-evident flight recorder for AI agents

Proof of what your AI agents actually did

Tracekit checks each tool call your agent makes before it runs, and risky calls wait for a person to approve them. Every action is signed into a tamper-evident log by a process the agent can't touch, so you can put agents on real systems and show what they did: your customers and auditors can verify the record themselves, offline.

PyPI Works with 42 agents and frameworks CI MIT licence

8 of 8

tamper attacks caught
480 trials, with a witness (E1)

957 of 957

harmful calls stopped
11 classes, 1 false alarm in 972 (E17)

< 1 ms

added per tool call
0.91 ms at p99, signer round trip (E9)

8 of 8

insider attacks caught
a merge gate on every PR (E8)

Built like Certificate Transparency: signed records in an append-only log that independent witnesses cosign
Open file format · verifiers in Python, TypeScript and Go · MIT · runs on your own machines

Try it · Add it to your agent · What it proves · What's in it · Proof · How it works · Pilot it · Contribute · Docs


Your agent can act. Can you prove what it did?

Agents now run shell commands, edit code, query databases, send email and move money. Sooner or later one of them does something nobody expected, and three questions land on your desk:

  1. What exactly did it do?
  2. Was it allowed to?
  3. Can anyone trust the answer?

Your agent's own logs can answer the first two, roughly. They can't answer the third: the agent, a bug, or anyone with write access can change them, and nothing would show it.

Tracekit sits in the tool-call path, the way a flight recorder sits in a plane:

What Tracekit does
Stop Checks every tool call before it runs: allow, deny, or hold it for a person. An approval covers exactly the arguments that were approved, once.
Record Signs every call, decision and result into a hash chain held by a signer the agent can't reach. A lost event becomes a signed gap, never silence.
Prove Exports each run as one .tkb file. Anyone can verify it offline, even in a browser, and see VERIFIED, or FAILED with the record that was changed.

Here is one run, recorded both ways. A support ticket hides an instruction; the agent deletes 43 orders, then rewrites its own log and Tracekit's record so the delete reads as a lookup: