Skip to content

estack-read-agent-history: Codex timeline has activity but session-report and brief say none #49

Description

@ElliotDrel

Reproduction

On Windows, with local Codex rollouts present for 2026-09-21, run:

python C:\Users\2supe\.agents\skills\estack-read-agent-history\scripts\read_transcript.py --mode timeline --date 2026-09-21 --agent codex
python C:\Users\2supe\.agents\skills\estack-read-agent-history\scripts\read_transcript.py --mode session-report --date 2026-09-21 --agent codex
python C:\Users\2supe\.agents\skills\estack-read-agent-history\scripts\read_transcript.py --file C:\Users\2supe\.codex\sessions\2026\09\21\rollout-2026-09-21T08-57-38-01a0c40b-1fa8-7eb3-9214-261fb31dafbe.jsonl --mode brief

Actual

timeline lists 14 activity blocks and 17 Codex sessions from 8:30 AM to 7:02 PM local. session-report prints (no user activity in range). brief on a participating rollout prints (no user prompts) and (no assistant messages) while counting 140 exec calls. The same behavior occurred on other September 21 rollout files. Codex app read_thread can retrieve user messages and assistant responses for those thread IDs.

Expected

session-report should summarize the Codex activity found by timeline, and brief should expose the normalized user/assistant messages for those rollouts.

This caused a day-backfill evidence audit to miss potential work. Please inspect whether the current Codex rollout schema is being normalized inconsistently across these modes.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions