Problem
CodeBurn only discovers Codex session files under ~/.codex/sessions/YYYY/MM/DD. When a conversation is archived, Codex moves its rollout file to the flat ~/.codex/archived_sessions directory. The next CodeBurn refresh no longer discovers that file, so its historical token usage disappears from reports.
Reproduction
- Run
codeburn report --provider codex and note the usage total.
- Archive a Codex conversation.
- Refresh the report.
- Usage from the archived conversation is missing, although its JSONL file still exists under
~/.codex/archived_sessions.
Observed with CodeBurn 0.9.15 and current Codex Desktop storage.
Proposed fix
Discover valid rollout-*.jsonl files from both the date-partitioned active sessions directory and the flat archived sessions directory, using the same metadata validation and project attribution for both. Add a regression test for an archived-only Codex home.
Problem
CodeBurn only discovers Codex session files under
~/.codex/sessions/YYYY/MM/DD. When a conversation is archived, Codex moves its rollout file to the flat~/.codex/archived_sessionsdirectory. The next CodeBurn refresh no longer discovers that file, so its historical token usage disappears from reports.Reproduction
codeburn report --provider codexand note the usage total.~/.codex/archived_sessions.Observed with CodeBurn 0.9.15 and current Codex Desktop storage.
Proposed fix
Discover valid
rollout-*.jsonlfiles from both the date-partitioned active sessions directory and the flat archived sessions directory, using the same metadata validation and project attribution for both. Add a regression test for an archived-only Codex home.