Codex Desktop renders :codex-followup directives as raw text instead of action buttons
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using?
Codex Desktop 26.831.21537 (build 7579)
What platform is your computer?
macOS 26.6.2, arm64
What issue are you seeing?
Suggested follow-up actions emitted by Codex are displayed verbatim as internal markup instead of being rendered as clickable follow-up buttons.
Observed output:
- :codex-followup[Compare project applications]{prompt="Show me where an ATS and an STS would sit in a typical project single-line diagram."}
- :codex-followup[Prepare selection checklist]{prompt="Prepare a practical ATS-versus-STS selection checklist for reviewing project specifications."}
- :codex-followup[Review product suitability]{prompt="List the technical information we should request before considering the STS for a project."}
The entire directive, including :codex-followup, the label, and the prompt attribute, is visible in the conversation UI.
What steps can reproduce the bug?
- Open a normal Codex Desktop conversation.
- Have the assistant answer a question and include one or more supported
:codex-followup[Label]{prompt="..."}directives at the end. - Observe the rendered assistant message.
The issue occurred with three directives formatted as Markdown list items.
What is the expected behavior?
Each directive should render as the intended clickable suggested-action control. If the directive cannot be parsed, the UI should fall back to a clean user-facing label rather than expose internal markup.
Additional information
A screenshot was reviewed locally and clearly showed all three raw directives. No user files, account information, or private project content are included in this report.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Reproduce the issue in a Codex Desktop conversation using the listed :codex-followup directives, then trace the assistant-message rendering path; done means directives become clickable suggested-action controls or fall back to clean labels without exposing markup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100