-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Bug
Codex runs show only π· dir: codex-test in the footer, with no model name. By contrast, Claude runs show π· dir: codex-test | opus 4.6 (1M) Β· plan β the model name and permission mode are visible.
Reproduction
- Send any prompt to the Codex engine chat
- Wait for completion
- Footer shows:
π· dir: codex-test - Compare with Claude: footer shows
π· dir: codex-test | opus 4.6 (1M) Β· plan
Expected
Footer should show the Codex model name, e.g. π· dir: codex-test | codex-mini-latest
When approval policy or reasoning overrides are active, those are shown (e.g. safe, high appeared correctly in O3 and O5 tests), but the base model name is missing.
Context
- The
/exportoutput showsModel: Codex(capitalised, not the actual model ID) - The model name in the footer comes from
StartedEvent.metaβ Codex'sthread.startedevent may not populate model info, or the runner may not extract it - The
/configpage showsModel: default Β· codex-mini-latestβ so the config knows the default model, but it doesn't appear in run footers - Override labels (safe, high) DO appear because they come from
EngineOverrides, not from the Codex CLI response
Affected files
src/untether/runners/codex.pyβtranslate()may not be extracting model info from Codex JSONL events intoStartedEvent.metasrc/untether/markdown.pyβmeta_line()formatting
Version
v0.35.0rc11 β found during Codex integration testing
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working