Skip to main content
Agent Journal 2.0 is the current Journal line, on main. It is not yet released, and breaking changes are expected before 2.0.0. Checked against markpollack/agent-journal@453c1d1, snapshot 2.0.0-20261108.225512-21.
journal-ocsf-writer writes packages. Its command line is OcsfWriterTool; its API is CliCapture, OcsfRunWriter and FinalAssembly.

Commands

A spec with several sources needs a reviewed final-assembly profile, or --evidence-log, which writes an unvalidated evidence log, never a final combined execution.

Launching a CLI

launch (CliCapture) starts the CLI’s streaming invocation, reads its raw standard output into the writer (an independent byte-for-byte copy is written before the writer sees each chunk), archives the CLI’s native session file unchanged beside the package, and freezes the expected-source manifest from the independent copy after acquisition. With a reviewed final-assembly profile, it then assembles the declared sources into a new final package. A launch needs the CLI installed and signed in; this page shows no recorded launch. Three facts stay separate, in the result and in the package: Reaching EOF never means the CLI succeeded: a CLI that exits non-zero after a complete stream is a completely acquired failed run. CLI versions. Claude Code’s stream reports its version, so no version command runs. Codex and Antigravity streams report none, so codex --version or agy --version runs exactly once before launch. The native session file is located by the session id the stream reported and copied by bytes with its hash; it is never parsed for enrichment or version discovery.

Assembling several sources

FinalAssembly.assemble(acquisitionManifest, outDirectory) validates an acquired-execution manifest and writes a new final package. File hashes, extents and route bindings are checked before the output is opened, and original inputs are never modified. A required role without an input is declared missing and makes the assembly incomplete, never silently complete. Which CLIs and routes each command accepts is in CLI support.