[Bug]: Codex follow-up suggestions render as raw codex-followup markup

[failaip12]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

1. Open a conversation in T3 Code using the Codex provider.
2. Have Codex complete a task and suggest follow-up actions.
3. When its response includes :codex-followup[...] directives, view the completed message.

The observed response contained several suggestions in this format:

:codex-followup[Prepare print version]{prompt="Prepare the document for printing."}

Asking codex to suggest a follow up should reproduce it.

Expected behavior

Follow-up suggestions should display in a readable form without exposing directive syntax. If interactive follow-up actions are supported, the label should let the user select the associated prompt. Otherwise, readable plain text would be a useful fallback.

Actual behavior

The complete directive appears literally, including :codex-followup, brackets, and the prompt attribute. The suggestions are not interactive.

In the same response, the generated PDF link rendered correctly. Three follow-up suggestions below it all appeared as raw markup.

Impact

Minor bug or occasional failure

Version or commit

Installed T3 Code Nightly: 0.0.41-nightly.20260911.1564 Upstream source inspected: cd64ad384e40988f57e4caa5a3f74f25ca5ef450

Environment

• Linux / CachyOS - T3 Code desktop AppImage - Codex provider

Logs or stack traces

Screenshots, recordings, or supporting files

Workaround

Copy the text inside prompt="..." into a new message, or ask Codex to write follow-up suggestions as plain text.

[juliusmarminge]

Triage

Confirmed as a renderer compatibility gap, same family as #5813 (:codex-file-citation used to show up raw). Not a duplicate of that issue (it's closed and citation-only). No open PR covers this.

Codex is emitting a third markdown text directive:

:codex-followup[Prepare print version]{prompt="Prepare the document for printing."}

T3 only parses two Codex directives today (:codex-file-citation and ::artifact-template) in packages/client-runtime/src/codexMarkdownDirectives.ts. The name gate rejects anything else, so follow-ups stay literal. That matches the report: the PDF/citation in the same message rendered, the three follow-ups did not, and they were not clickable.

Filed under desktop, but the bug is shared:

• packages/client-runtime/src/codexMarkdownDirectives.ts (parser / copy adapters)
• apps/web/src/components/ChatMarkdown.tsx (web + desktop)
• apps/mobile/src/features/threads/ThreadFeed.tsx (mobile)

The prior fix to copy is #8584. T3 has no generic suggestion-chip surface (Claude prompt_suggestion is dropped on purpose). Closest interactive pattern is artifact-template Use template, which appends a prompt to the composer.

Severity: minor bug. Workaround (copy prompt="..." or ask for plain text) is fine.

Suggested fix: extend the existing directive plugin. Minimum is readable label text + copy. Better is chips that fill the composer with the prompt attribute. Cover web, desktop, and mobile; leave code/escaped/malformed/incomplete streaming examples literal, same as citations.

A reliable Codex prompt would help QA but is not required to implement — the syntax in this issue is enough for fixtures.

Related:

• [Bug]: Codex artifact citations render as raw codex-file-citation markup #5813 — raw :codex-file-citation (fixed)
• fix(web,mobile): render Codex citations and artifact templates #8584 — shared citation + artifact-template renderer
• fix(chat): render Codex source citations #9605 — different Codex source-citation markers; not this

[Andrew-Forster]

I’ll pick this up. I’ll keep the change in the existing shared Codex directive renderer, cover web/desktop and mobile, and add focused tests for the raw-markup regression. I’ll open a PR once it’s working.

[Andrew-Forster]

Implemented in #11355.

It extends the existing shared Codex directive renderer, adds composer actions on web/desktop and mobile, keeps passive fallbacks readable, and covers malformed, code, copy, and mobile-link cases. The branch is rebased onto current main; 227 focused tests and client-runtime, web, and mobile typechecks pass.

[YoungPhlo]

Seeing the same. Over the last few days, raw :codex-followup[...] outputs have appeared at the end of Codex turns. I explicitly do not ask for follow-up suggestions.

I typically see two or three suggestions after the normal completion message, with the label and prompt attribute rendered literally.

Environment:

• Surface: T3 Code (Alpha) desktop
• T3 version: 0.0.40
• OS: Windows 11 Pro, build 26200

[Aarya2004]

Another occurrence observed on October 4, 2026 in a T3 Code conversation using the Codex provider on a macOS-hosted environment. Further details below:

• Client: T3 Code (Nightly), macOS desktop app
• App version/build: 0.0.46-nightly.20261003.2623
• Connected server: 0.0.46-nightly.20261003.2623
• Platform: macOS, Apple Silicon (arm64)

After an artifact-editing task, the assistant emitted three follow-up directives as Markdown list items. All three appeared as literal markup rather than usable actions.

An example:

- :codex-followup[Review document]{prompt="Review the revised document."}

The artifact skill used in this session explicitly instructs Codex to emit this syntax, so this can recur during ordinary artifact workflows without the user requesting special markup.

🤖 AI-assisted comment