Rank, 14 days: 8 on the Claude Code sheet
93 people reported

All time, since Sep 14, including 66 thumbs-up on GitHub.

Mid-turn assistant text not shown

“The recap says e.g. "I looked at the header and made a proposal … Should I implement it?", but the proposal itself was never written as text in the turn.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/themes/234/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Fading. 3 reports and thumbs-up in the last 7 days and 15 the week before, down from 53 a week at the late-October peak. Not fixed, but the vendor replied, Oct 22.

10 bugs in this theme

  1. Next-step box hides the answerNo workaround yet41 people
  2. Text emitted as hidden thinkingNo workaround yet18 people
  3. Mid-turn text shown as summaryNo workaround yet11 people
  4. Mid-turn text replaced by summaryHas a workaround9 people
  5. Text before question box hiddenNo workaround yet8 people
  6. Mid-turn text replaced by summaryNo workaround yet7 people
  7. Long tool output not relayed4 people
  8. Reply saved as thinking blockNo workaround yet3 people
  9. Unexpandable summary hides messagesNo workaround yet3 people
  10. AskUserQuestion missing on mobileHas a workaround2 people

What's included

  • Explanation written before an AskUserQuestion, permission prompt or next-step question box never appears; only the box is visible
  • Prose between tool calls is stored as a thinking block and shown as a one-line, non-expandable grey summary, dropping details and code blocks
  • Desktop app, Remote Control mobile view and SDK-driven apps show a paraphrase (sometimes in another language) or nothing in place of the reply
  • Model continues as if the user read the full text ("as I explained above") and asks approval for content never shown
  • Transcript lacks the text block, so hooks reading the transcript cannot find what the assistant wrote

Not included

  • Messages the user types during a running turn being read as tool output or absorbed mid-turn
  • Thinking blocks displaying or collapsing in turns with no tool call

Original reports27, newest first

  1. Mid-turn assistant text replaced by summary and missing from transcript JSONL#108007
  2. Senseless question cards you can't turn off#106440
  3. Thinking "summaries" confuse models: they think they said X, but the user saw Y#106043
  4. The "· summary" line shown in place of mid-turn assistant text is a server-generated summary of a progress-update block, and it can state the opposite of what the model wrote; the TUI presents it as if it were Claude's message#105796
  5. Intermediate messages between tool calls collapsed into unexpandable summary#105174
  6. Text before AskUserQuestion / a permission prompt often never reaches the user (written to thinking, not as a text block)#105148
  7. Mid-turn replies to user messages collapsed into a non-expandable grey "summary" line#104946
  8. [Desktop] Transcript view "Normal" replaces assistant text before tool calls with a one-line summary#104512
  9. Desktop Code tab: text preceding question box sometimes not rendered#104131
  10. Desktop Code tab: next-step box (wrap_up) asks for approval of a proposal that was never shown as text#103169
Show all 27Show only the newest 10
  1. Desktop app (Code tab): the end-of-turn summary box can replace the whole answer#103135
  2. Desktop app: text written before a question box (AskUserQuestion / next-step box) isn't shown#103084
  3. Desktop Code tab: wrap_up question box shows no context, and it overrides a user CLAUDE.md rule that requires context#103036
  4. Desktop Code tab: end-of-turn question box asks for approval of content that is not shown in the chat#102857
  5. Text written between two tool calls reaches the user only as a one-line thinking summary (13/13 repro)#102807
  6. Desktop Code tab: next-step box (wrap_up with an ask) can end the turn before the reply is written#102132
  7. [Remote Control / Projects] AskUserQuestion from a Remote Control session never appears in the mobile app; thread stays stuck#102055
  8. Assistant text written before a tool call is shown to the user only as a one-line summary#101273
  9. AskUserQuestion dialogs in Remote Control sessions only render on the desktop, not on mobile / claude.ai#100478
  10. [Desktop app] Assistant messages shown to the user are replaced by paraphrased (often English) "thinking" text, and replies drift into English for a Japanese-speaking user#99641
  11. Messages meant for the user are sometimes emitted as hidden thinking before a tool call#97504
  12. Remote Control (mobile): assistant text before/between tool calls is replaced by a summary, with no way to disable it#97418
  13. Desktop app displays assistant reply text that the transcript records only as a (summarized) thinking block#96947
  14. Opus 5.5: instructed verbatim relay of a tool output over ~230 chars is never emitted as text when a tool call follows — the block is generated inside thinking (constant 274 output tokens, no text block on the wire)#96288
  15. Opus 5: prose between tool calls returned as summarized 'narration' thinking blocks since 2026-09-11 — code blocks dropped, Desktop never shows them, model believes user saw it#95764
  16. Sonnet 5 omits text content and shows only thinking summary before AskUserQuestion#95621
  17. [Desktop] Normal view shows thinking summaries that look like normal chat messages from Claude#94354

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.