One log for all your agents.

Every action, result, approval, and error can be reconstructed and inspected by you or any of your agents, forever.

Works with Claude Code, Codex, Assembly Line, and any runtime that speaks Provenance’s OTLP Logs contract.

Open Provenance↗Read the architecture↗

Claude Code · Codex · Assembly Line · OTLP Logs

CANONICAL USER LEDGER　│　REPRESENTATIVE DATA

Ledger

One ordered record across every agent.

Head: #18,432
Recent events: 24
Agents: 3
Captured: 100%

⌕　Search events, tools, agents, files… ⌘ K☷　All fidelity　⌄24 of 24

SEQTIMEACTORKINDEVENTFIDELITY

#18,43214:06:23CCodextool.resultAdded the modular ledger interfacecaptured

#18,43114:06:21CCodextool.callapply_patch · LedgerTable.tsxcaptured

#18,43014:05:58CCodexmessage.assistantThe ledger stays primarycaptured

#18,42914:05:41CCodexmessage.userBuild a clean ledger interfacecaptured

#18,42814:05:15WWatchercapture.batch12 events accepted · 84 mscaptured

#18,42714:04:52CCodexfile.changedweb/src/theme/tokens.csscaptured

#18,42614:04:27CCodexapprovalDomain pattern approvedcaptured

The Lighthouse at Honfleur, Georges Seurat, 1886. oil on canvas

ONE TASK THROUGH PROVENANCE

Continue from cited evidence.

A new agent needs to continue an authentication refactor. It searches the session index, narrows results through slim event headers, and loads the turns and tool traces that changed the code.

The handoff names the files, decisions, failed attempts, and open work. Each claim cites the message, tool call, result, or artifact behind it.

01Find the session
02Narrow the evidence
03Load tool traces
04Verify each claim
05Continue the work

Let every agent pick up where the last one stopped.

Provenance gives every agent the same inspectable history across sessions and runtimes. Each handoff can cite the exact events behind it.

Pick up work a week later.

The CLI and MCP expose the same read model, so agents can find evidence without loading a full transcript.

↳Session and agent discovery
↳Event search by time, kind, actor, tool, and entity
↳Turn and tool traces
↳Related-event traversal
↳Artifact retrieval
↳Compact, cited handoff bundles

Record every agent automatically.

The Provenance watcher tails transcripts from Codex, Claude Code, and other JSONL runtimes. Native adapters emit the same event contract from other frameworks.

↳Ambient transcript tailing
↳Native runtime adapters
↳OTLP log ingestion
↳Crash-safe, idempotent batching
↳Historical backfill
↳Non-blocking capture

Keep one history across every runtime.

Messages, tool calls, results, approvals, errors, retries, and session boundaries enter one append-only sequence for each user.

session.*
message.*
tool.*
approval.*
agent.*
capture.*

Install capture for past and future sessions.

The installer sets up the CLI, MCP reader, evidence skills, and transcript watcher. It can import past history and capture new sessions.

npx -y provenance-log@latest install \
  --api-url https://provenance.example.com \
  --user USER --token TOKEN \
  --hosts codex,claude-code

Clear product boundaries.

Repositories own current files. Mirror owns connected context. Summaries remain cited, derived views. Provenance owns the evidence sequence across runs.

QUESTIONS, ANSWERED

What to know before you start.

01Does the agent need to call a logging tool?＋

No. Transcript watchers and native adapters capture events outside the model loop.

02Can an event be changed later?＋

No. The ledger is append-only. Corrections and later observations become new events.

03Does Provenance summarize my history?＋

Provenance stores events. Deterministic queries and cited handoff bundles derive views from them.

04Is Provenance tied to one agent framework?＋

No. It works with Claude Code, Codex, Assembly Line, and other runtimes that speak its OTLP Logs contract.

Provenance

START HERE

Let the next agent see what actually happened.

Open Provenance↗