Skip to main content
When your agent runs on your own machine, Helix reads its traces from local sources — the transcripts your coding agent already writes, or a JSONL export. Everything stays on disk; nothing is uploaded.

Claude Code transcripts

Reads sessions your Claude Code agent writes under ~/.claude/projects/. Works out of the box — point Helix at the project and it finds the runs.

Codex transcripts

Reads Codex session transcripts (~/.codex/sessions/) in the same way.

Pi / Oh My Pi transcripts

Reads Pi and Oh My Pi session transcripts for agents built on those runtimes.

JSONL export

Any agent that can emit a trace in JSONL/NDJSON form — one run per line — can be read as a source. Bring your own format; gzipped files are supported.

​
How it connects

Point Helix at the source and it binds it to Evaluate and Diagnose:
.mutagent/config.yaml
A single local source needs no credentials. For a JSONL export, point paths at your files. See the config reference for every key.
Have traces in a hosted observability platform instead? See OpenTelemetry sources.