v0.1.24

Changed

• Treat successful git commit commands in Codex tool logs as committed turns, even when the commit happens outside the launch repo.
• Keep the commit indicator in sync for resumed sessions by scanning tool log output.

v0.1.23

Changed

• Keep fresh sessions on codex:new until a real user prompt arrives by ignoring bootstrap messages.
• Only flip to running/done after a real prompt is seen, preventing stuck titles on new/resumed sessions.

v0.1.22

• Pin the active log once a resume signal is detected to prevent oscillating between logs.

v0.1.21

• Check for resume switches even while the current log is actively receiving events.

v0.1.20

• Add --status to print the resolved title and active log path without modifying the tab title.\n- Document the debug log env var and status command.

v0.1.19

• Always write a lightweight debug log to ~/.codex/log/codex-title.log to capture which log path is selected or switched.

v0.1.18

• Pick the most recent resume line regardless of timestamp to avoid missing fast /resume events.\n- Track history updates by file size and start from the current end to avoid scanning old sessions.

v0.1.17

• Switch to resumed sessions even if the current log remains active by prioritizing resume signals.\n- Use history session IDs as authoritative without comparing log mtimes.

v0.1.16

• Follow the active session via ~/.codex/history.jsonl when /resume does not emit a usable TUI signal.\n- Scan a deeper tail of the TUI log to avoid missing resume lines during heavy logging.

v0.1.15

• Prefer the TUI resume log (from ~/.codex/log/codex-tui.log) when /resume switches to an older session log.