Skip to main content
Agent Journal has two lines with different, incompatible formats.

Use 1.x (1.11.0) if

  • you depend on a released artifact, or on released Agent Client (0.32.0 pins Journal 1.10.0);
  • you use journal-core, the 1.x event and analysis files, the six capture adapters, or the DuckDB queries.

Use 2.0 (main) if

  • you want one portable OCSF events.jsonl per run, checked by an independent oracle;
  • you build against Agent Client main.
Resolve the timestamped snapshot from the Central snapshot repository and name the main commit you checked against; see Getting started (2.0). Breaking changes are expected until a release.

No upgrade path

2.0 does not read 1.x files and 1.x does not read 2.0 packages. To move a run to 2.0, re-capture it or replay the CLI’s native output (its stream or session file) through 2.0: 2.0 reads the CLI’s own files, not 1.x records.

Concept map

Not in 2.0

  • Gemini CLI and Grok CLI capture
  • The EvalSubject seam and the feedback service
  • Even-split cost attribution
  • The content cap and its modes

New in 2.0

  • GitHub Copilot CLI (experimental); see CLI support
  • The independent oracle and OcsfReaderTool; see Reading packages
  • Child cores for sub-agents
  • Version-neutral Claude Code SDK and Codex exec routes: the CLI version is recorded, not gated