Expand description
Text-free reduction of one Codex rollout file into the events of the thread that owns it.
Every rollout line carries a contiguous ordinal. A forked child copies part of its parent’s
history into ordinals 1..subagent_history_start_ordinal; those lines describe the parent and
are skipped. Each completed model response writes one token_usage_record, so requests are
reconstructed from those records and the response items between them.
Structs§
- Agent
Send - A spawn, follow-up, or message this thread queued for another thread.
- Child
Completion - A child’s completion, recorded in the parent’s rollout when the child’s turn finishes.
- Codex
Request - One completed model response.
- Codex
Tool - One tool call emitted by a response.
- Rollout
Thread - Text-free events of one Codex thread, from its own rollout lines only.
- Unrecorded
Responses - Responses whose usage Codex never recorded.
- Usage
- Usage of one completed response, as recorded in
token_usage_record.
Enums§
- Skip
Reason - Why a rollout file contributes no thread.
Functions§
- parse_
rollout_ file - Reduces one rollout file to the events of the thread that owns it.