agenttraces

Give your agent the work that came before.

AgentTraces captures coding-agent sessions and makes them searchable from the CLI or any MCP client. Your current agent does the reasoning; AgentTraces retrieves the evidence.

npx agenttraces up

Detect supported coding agents, start private capture, and install the local MCP connection.

Search returns a small set of authorized traces—not a dump of every event. Each result keeps its provenance so an agent can retrieve only the evidence it needs.

Find past work in one sentence

Search the way you remember the work. AgentTraces filters first by what you are allowed to see, then ranks matching traces and evidence.

Remember the fix, not the filename

Find the authentication regression we fixed last month.

AgentTraces searches the work you can access, then returns compact evidence with the repository, source, time, and trace ID intact.

Continue an investigation

What did we learn about the queue timeout?

Your current agent can retrieve the earlier commands, decisions, and outcome instead of repeating the investigation from scratch.

Recover the work behind a change

Show me the trace behind PR #428.

Git and pull-request evidence narrow the search. The result stays linked to the native session it came from.

A trace is evidence, not another chat transcript

A result opens into the smallest useful view of the work: who did it, where it happened, what changed, and the native events behind the answer.

Illustrative interface · synthetic trace data

payments-api / PR #428

Fix webhook replay handling

team
Agent
Codex
Branch
fix/webhook-replay
Events
83
Trace
tr_01J8…42E
Question

Find why replayed events create duplicate invoices.

Reasoning

The event ID is checked after the invoice side effect.

Commandrg -n "event_id|invoice" src test
Outcome

Commit the unique event record before invoice processing.

Capture once, retrieve wherever you work

On your machine

  1. 1 Discover native session artifacts
  2. 2 Scrub secrets before enqueue
  3. 3 Encrypt the pending local spool

In the cloud

  1. 4 Normalize events with provenance
  2. 5 Apply namespace permissions
  3. 6 Retrieve through CLI or MCP

Personal traces are private by default. In a team, the owner defines the default visibility and retention policy.

Seven local collectors, one trace model

Local adapters understand all seven native formats. Claude Code and Codex lead the first end-to-end path; the remaining rows show collector coverage, not a promise of full product support.

Claude CodeJSONL session historycollector ready
CodexNative rollout historycollector ready
CursorLocal session databasescollector ready
OpenClawSession artifactscollector ready
ConductorAgent workspacescollector ready
AntigravityAgent session filescollector ready
GitHub CopilotLocal conversation datacollector ready

Make earlier work available to the next agent.

Install AgentTraces, keep new sessions private, and ask your current agent for the work you remember.

npx agenttraces upView on npm