[Bug]: Assistant citations render as raw t3-citation markup in queued messages #12331

Activity

1. repparw commented on Sep 17, 2026

   

   repparw

   on Sep 17, 2026

   ContributorAuthor

   More actions

   Screenshot from the report (hosted on my fork since I can't attach files here directly):

   
2. juliusmarminge commented on Sep 17, 2026

   

   juliusmarminge

   on Sep 17, 2026

   Member

   More actions

   Triage

   Decision: Accept
   Classification: Bug
   Severity: Minor (P3)
   Confidence: High
   Repro: Source-confirmed. Reporter steps and screenshot are sufficient; no extra environment details are required.
   Area: apps/web (chat timeline queued bubble). Desktop shares this row. Mobile is a different renderer.

   Already fixed on main? No (6deac7a92). Also present on v0.0.42.
   Duplicate of: none.

   Summary

   Confirmed. Citing an assistant response serializes as [Assistant quote](t3-citation://v1/...) in the composer. A sent user bubble runs that string through ChatMarkdown, which allowlists t3-citation and returns AssistantCitationChip. A follow-up queued while the turn is still running does not: QueuedMessageTimelineRow prints queuedMessage.prompt as plain whitespace-pre-wrap text, so the percent-encoded href spills across the dashed bubble until the turn ends and the message sends normally.

   This is leftover from #11673 (queued follow-ups, merged 2026-09-15), not a break in #9146 (citations, merged 2026-09-02). The queue path stored the raw citation markdown and never reused the sent-message renderer.

   The screenshot matches: raw t3-citation://v1/8baf8577-… link, then the typed reply, then Clock + Queued / send / cancel.

   Diagnosis

   Composer citations are self-contained Markdown links. That is intentional and unchanged:

   export function serializeAssistantCitation(citation: AssistantCitation): string {
     return `[Assistant quote](${formatAssistantCitationHref(citation)})`;
   }

   While a turn is running and follow-up behavior is queue, ChatView enqueues that raw prompt. The queued bubble then renders the string literally:

     const text = queuedMessage.prompt.trim();
     // ...
           {text.length > 0 ? (
             <div className="whitespace-pre-wrap break-words text-sm">{text}</div>
           ) : null}

   A sent user row goes through UserTimelineRow → CollapsibleUserMessageBody → UserMessageBody → ChatMarkdown, which already allowlists t3-citation and returns AssistantCitationChip.

   Same class of leak: a queued t3-context:// file/terminal chip would also show as a raw link. Out of scope for this report, but the same ChatMarkdown pass would cover it. No new citation protocol or store change is needed.

   Mobile is not this bug. Pending outbox rows are fake user messages and run renderAssistantCitationsAsText before markdown, so they become readable > Assistant quote: blocks instead of a raw href.

   Related issues

   Not a duplicate. Same class (raw markup in chat) as the Codex issues, different scheme and surface:

   Issue	Why different
   #9146	Shipped citations. Sent user messages and the composer already chip them. This gap is the later queued row.
   #11341	Raw :codex-followup in assistant completions.
   #11810	Malformed Codex markdown links in assistant output.
   #5813	Closed. Raw :codex-file-citation artifacts.
   #9605	Codex source citations (:codex-citation), different scheme.

   Recommended next step

   Accept and fix in apps/web only:

   1. Render queuedMessage.prompt with ChatMarkdown (reuse UserMessageBody if the queued bubble can take skills / markdownCwd from TimelineRowCtx). Do not add a second citation parser.
   2. Keep the dashed chrome, Clock + Queued footer, and send/edit/remove actions.
   3. Add a focused test that a queued prompt containing serializeAssistantCitation(...) does not dump the raw t3-citation:// href and does render AssistantCitationChip.
   4. Optional: the same pass will chip t3-context labels if renderContextReference is wired; not required to close this.

   Do not change serializeAssistantCitation, the enqueue payload, or provider expansion (expandAssistantCitationsForProvider). Those paths are fine; only the queued preview is wrong.

   Workaround

   Wait until the turn ends so the follow-up sends as a normal user message, which already renders the chip. No settings workaround.
3. juliusmarminge

   added

   bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.

   acceptedfeature request acceptedfeature request accepted

   via-triageFiled through npx t3 triageFiled through npx t3 triage

   on Sep 17, 2026
4. maria-rcks

   closed this as completedin #12403on Sep 20, 2026