AskQuestion rendering hides assistant prose body when both are in the same turn

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When the assistant writes a markdown text block and then calls the AskQuestion tool in the same turn, the chat UI renders only the question card and silently drops the text body — even though the text is present in the on-disk transcript. The user sees an empty void above the question card and loses all the context the agent wrote to frame it.

Steps to Reproduce

Author or use an Agent Skill where the agent writes 1–3 lines of markdown prose (header, paragraph, bullets, blockquote — any prose body) and then calls the AskQuestion tool in the same assistant message.
Run the skill; reach the point where that turn fires.
Observe the chat pane.
A real on-disk transcript event (from ~/.cursor/projects//agent-transcripts//.jsonl) that triggers this:

{“role”:“assistant”,“message”:{“content”:[
{“type”:“text”,“text”:“Pre-flight result — Full mode available\n\nAll sibling repos detected:\n\n| Repo | Status |\n|—|—|\n| ../userpref | Present |\n…”},
{“type”:“tool_use”,“name”:“AskQuestion”,“input”:{ … }}
]}}

Expected Behavior

Both the markdown text body and the AskQuestion card render in the chat pane, in order — exactly like any other assistant turn that mixes prose with a tool call.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.4.17 (Universal)
VSCode Version: 1.105.1
Commit: 93e603f703cd553a6bb3644711a3379bbbb31180
Date: 2026-05-13T21:39:55.724Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

For AI issues: which model did you use?

claude opus 4.7 xthinking

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @Kevin_Zana,

Thanks for the detailed report, complete with transcript evidence. This is a confirmed bug.

A fix for this was shipped very recently (after your current build). Please update Cursor to the latest version: Cmd+Shift+P > Attempt Update, then restart. That should resolve this.

If the issue persists after updating, let me know and I’ll investigate further.