CLI resume truncates tail of last assistant message while VS Code shows full response (0.144.6, macOS)
What version of Codex CLI is running?
codex-cli 0.144.6
What platform is your computer?
macOS (Darwin arm64)
What issue are you seeing?
After the terminal resets and an existing Codex CLI chat is opened again, the visible transcript can contain only the first section of the last completed assistant response. Later sections of that same assistant message are absent from the CLI view.
The complete assistant response is visible for the same conversation in the Codex VS Code extension, so the response appears to be persisted and available to another client. This points to CLI resume/replay/rendering rather than model-output truncation or session-data loss.
The affected response contained Markdown headings, numbered sections, and fenced HTML examples. The CLI showed the first numbered contract section but omitted the later independent slot-metadata section and the remainder of the response.
This resembles #29218, but that report was closed after being associated with a disabled terminal_resize_reflow path. This reproduction is on current 0.144.6, where the feature is enabled by default, and the symptom recurs specifically after reopening the chat.
Steps to reproduce
- Build a multi-turn Codex CLI conversation.
- Have the assistant finish a structured Markdown response with at least two sections and a fenced code example between them.
- Let the terminal/session reset or close the CLI.
- Reopen the existing chat with the CLI resume/session picker.
- Compare the last assistant message with the same conversation in the VS Code extension.
Expected behavior
The resumed CLI transcript should display the complete persisted assistant message, matching the VS Code extension.
Additional information
No repository names, source code, or private conversation text are included in this report. The reporter can submit the affected thread through the in-product /feedback dialog if maintainers need the session logs.
1 Comment
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action