Audit trails for AI coding agents (Claude Code, Codex, Cursor)
Updated · 8 min read
What tools give me an audit trail for AI coding agents like Claude Code and Codex?
Start with what you already have: git history, pull requests and CI show what changed in the code. Each coding agent also has its own session or audit records. To review work across tools, connect the original request, exact revision, relevant checks, permissions and acceptance decision. OrgX keeps that linked work record; inspect the evidence your existing tools already provide before adding another system.
What an audit trail for coding agents should answer
- What was the agent asked to do, and by whom?
- What did it change (files, commands, pull requests, deploys)?
- What was it allowed to do, and did it ask before anything risky?
- How was the result checked: tests, review, a person's sign-off?
- What is still open, and what should the next agent or person know?
What each layer records
- Git and your code host: every commit, pull request, review and merge. This is the most trustworthy record of what changed, and it already exists.
- CI: which checks ran on which commit and whether they passed.
- Claude Code: permission prompts and hooks on the machine, and OpenTelemetry export of usage metrics and events that you can send to your own monitoring. Teams on Anthropic's business plans also get usage analytics.
- Codex: an approval policy and sandbox per session, and local session logs of the conversation and the commands it ran.
- Cursor: agent chat history in the editor, command allowlists, and admin audit logs on business plans.
- Observability and evaluation tools can associate traces with task or project metadata and review feedback. Check whether your workflow links those records to the exact deliverable, its requirements and the acceptance decision; a successful trace alone does not establish acceptance.
The gap: one record across tools
A feature might start in ChatGPT, get built in Claude Code, get fixed in Cursor and get reviewed by a person. Logs and reviews can be distributed across those tools. An accountable handoff links them to the same deliverable revision, so a client or teammate can inspect the request, checks and acceptance without reconstructing the history.
How OrgX fills it
- Agents connect through the OrgX MCP server and plugins, read the task and the decisions already made, and write back what they did.
- Each finished piece of work carries a receipt: what was asked, what authority the agent had, what changed, the evidence (pull request, test run, URL), and whether it was verified.
- The receipt format is open: Agent Work Receipt v0.1 is a JSON Schema you can emit and validate without an OrgX account.
- OrgX-managed sends, deploys and spend pass through its approval gates, and the approval stays with the work. Actions outside OrgX retain their native permission policies.
- Honest limit: capture from Claude Code today needs the OrgX hooks installed alongside the plugin, and receipt coverage from Claude Code sessions is lower than from Codex. Git stays the source of truth for code changes.
Which record answers which question
| Question | Where the answer lives | Across tools? |
|---|---|---|
| What changed in the code? | Git, pull requests | Yes, per repository |
| Did the checks pass? | CI | Yes, per repository |
| What did the agent run on my machine? | Claude Code telemetry, Codex session logs, Cursor history | No, one log per tool |
| Why was it done, and who approved it? | OrgX record and receipts | Yes |
Questions people ask
Do I need a separate tool if I already have git history?
For small solo projects, git plus pull request descriptions may be enough. You need more when several agents and people share the work, when risky actions need approval, or when you must show a client or auditor who checked the work.
Does OrgX record every command an agent runs?
No. OrgX records the work: the task, decisions, approvals, evidence and outcome. Command-level logs stay in each tool (Claude Code telemetry, Codex session logs). Link to them from the receipt when they matter.
Can I use the receipt format without OrgX?
Yes. Agent Work Receipt v0.1 is a published JSON Schema with example receipts for Codex, Claude Code and OpenClaw, and a validator that works without an account.
Related
Proof for AI-delivered work
OrgX is proof for AI-delivered work — the operating record your agents and tools share.