GitHub issue #15594 in cline/cline, opened 2026-11-08 by rjvkn, records a report that the Cline CLI splits a single assistant message into separate transcript rows when the provider interleaves reasoning chunks with text chunks, so a Thinking row is injected between the two halves of one sentence and the answer reads as if it was cut off, while the model output itself is intact. The report traces the split to use-agent-events.ts starting a new transcript entry every time the stream switches type, and notes the VS Code task path already handles interleaved reasoning while the CLI handler has no equivalent gate.
Verbatim Excerpts from Cited Records
“The CLI splits a single assistant message into separate transcript rows when the provider interleaves reasoning chunks with text chunks.”
·
cline/cline (issue 15594 opening body, What happened section)
·
2026-11-08T06:14:10Z
·GitHub Issue ↗
“The `▶ Thinking:` row is injected between the two halves of the sentence, so the answer reads as if it was cut off. The model output itself is intact — this is a row-grouping bug in the CLI's stream handling, not a content issue.”
·
cline/cline (issue 15594 opening body, What happened section)
·
2026-11-08T06:14:10Z
·GitHub Issue ↗
“`apps/cli/src/tui/hooks/use-agent-events.ts` starts a new transcript entry every time the stream switches type:”
“One logical assistant message stays one contiguous block. Reasoning that arrives after text has started should not interrupt it — keep the reasoning row ahead of the message or merge it there, mirroring #9298.”
Counter-record: Issue remains open. API returned 2 comments; both were read. linear-code[bot] (2026-11-08) linked the report to CLINE-3756. shudhanshuman (2026-11-08) offered to work on the issue. No maintainer response appears in the thread. No retraction or correction appears in the thread. The claim documents only the original report, not a verified current state.
Falsification probe: If issue 15594 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.