pingdotgg / pingdotgg/t3code

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

Open
#11,341 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

accepted bug via-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

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
Image
Workaround

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in apps/desktop by reproducing a Codex conversation that includes :codex-followup directives and inspect the message-rendering path. Compare the raw response with the expected readable or interactive presentation, then verify that follow-up suggestions no longer expose directive syntax while the generated PDF link still renders correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.