Unverified50% confidenceFactExact time
Codex's `codex exec --json` streams JSONL output, the `turn.completed` event carries token data, and the cache count is already included in the input count.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/16/2026
First Seen
Valid until: 1/14/2027
Sources
Related Entities
Related Claims
UnverifiedHeadless mode runs detached from an interactive terminal via the claude -p command, and --output-format json can be specified to embed output into scripts, with JSON metadata containing information such as total_cost, num_turns, and duration_ms.70% similarUnverifiedBacktesting results can be exported as JSON files.68% similarUnverifiedUsing JSONL append writes instead of JSON overwrite writes is the standard practice for idempotent tasks: each line of JSONL is independent, and an interrupted write only loses the last line; with overwrite-style JSON, an interrupted write corrupts the entire file and progress returns to zero.67% similarVerifiedThe Claude Code SDK can return structured output in JSON format via the --output-format json parameter.66% similarUnverifiedCodex's session transcript JSONL rollout files are located at $CODEX_HOME/sessions/YYYY/MM/DD/rollout-*.jsonl; this layout comes from a 2025 feature request (openai/codex issue #2288) and is observed behavior rather than a documented contract.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1049115API
curl https://kongchang.com/api/v1/knowledge/claims/1049115MCP
get_claim(id=1049115)