gpt-5.4 is sometimes shown as gpt-5 for OMX/Codex sessions

[betive37]

CodexBar seems to show gpt-5 instead of the actual runtime model gpt-5.4
for some Codex sessions, especially OMX (oh-my-codex) sessions.

What I verified:

• In the original session logs under ~/.codex/sessions/*.jsonl,
  turn_context.model is gpt-5.4
• ~/.codex/log/codex-tui.log also records the same turns as model=gpt-5.4
• But in ~/Library/Caches/CodexBar/cost-usage/codex-v2.json, some of those
  same sessions are bucketed under gpt-5

Examples:

• Misclassified:
  • rollout-2026-03-29T10-03-22-019d371d-f275-78d3-86c0-f5a2ba95dc17.jsonl
  • Source: turn_context.model = gpt-5.4
  • CodexBar cache: days.2026-03-29.gpt-5 = [...]
• Correctly classified:
  • rollout-2026-03-28T11-18-17-019d323c-2c87-75b3-8566-15f873358216.jsonl
  • Cache includes lastModel = gpt-5.4

From my local cache scan, 29 out of 35 sessions bucketed as gpt-5 explicitly
contain gpt-5.4 in the source JSONL, and 30 of those are OMX sessions.

So this looks less like an actual model switch and more like a CodexBar
parsing/cache fallback issue.

Suggested model resolution priority:

1. turn_context.model
2. collaboration_mode.settings.model
3. Only fall back to family labels like gpt-5 if neither exists