Skip to content

[#80] test(compat): codex-tui.log opt-in in v0.134.0 does not affect JSONL session parser#90

Open
delexw wants to merge 1 commit into
mainfrom
fix-issue-80
Open

[#80] test(compat): codex-tui.log opt-in in v0.134.0 does not affect JSONL session parser#90
delexw wants to merge 1 commit into
mainfrom
fix-issue-80

Conversation

@delexw
Copy link
Copy Markdown
Contributor

@delexw delexw commented May 31, 2026

Summary

Codex v0.134.0 (PR #24081 "tui: make codex-tui.log opt-in") changed the TUI log file from being written unconditionally to requiring explicit opt-in. The file no longer exists at its default path unless the user enables TUI logging.

codex-trace reads session data exclusively from JSONL files at ~/.codex/sessions/ — it does not read codex-tui.log. The opt-in change therefore has no effect on session parsing or session discovery.

Changes

src-tauri/src/parser/entry.rs — adds regression test v0134_tui_log_opt_in_does_not_affect_jsonl_session_parser that:

  • Documents the v0.134.0 codex-tui.log opt-in boundary (codex-trace reads JSONL files, not the TUI log)
  • Verifies all four standard JSONL entry types (session_meta, event_msg, response_item, turn_context) parse correctly for v0.134.0 sessions regardless of whether the TUI log is present on disk

This follows the established compat-test pattern used for previous Codex version changes (e.g. log_db_log_writer_refactor_does_not_affect_jsonl_session_parser for v0.128.0).

Verification

  • cargo test --lib — 132 tests pass (including new v0134 test)
  • cargo clippy -- -D warnings — no warnings
  • npx vitest run — 128 frontend tests pass

Fixes #80

… affect JSONL session parser

Codex v0.134.0 PR #24081 made `codex-tui.log` opt-in. codex-trace reads
session data exclusively from JSONL files at ~/.codex/sessions/ — it does
not read the TUI log. The opt-in change therefore has no effect on session
parsing or session discovery.

Add a regression test in entry.rs that documents this boundary and verifies
all four standard JSONL entry types (session_meta, event_msg, response_item,
turn_context) continue to parse correctly for v0.134.0 sessions regardless
of whether the TUI log is present on disk.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Compat] Codex v0.134.0: codex-tui.log is now opt-in (no longer written by default)

1 participant