Reasoning/thinking content display in gateway streaming

NousResearch/hermes-agent · cluster 5892 · gateway

Data as of

8 open items. Fix attempted, not merged.

The short answer

4open issues
4open PRs
11items grouped
Known?
Yes. 11 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
4 issues and 4 PRs.

These issues and PRs concern bugs and features around how reasoning or chain-of-thought content (think blocks, Anthropic thinking blocks) is filtered, preserved, and displayed to users on platforms like Telegram during and after streaming. Topics include content leaking, content being silently dropped, and adding configurable collapsible display of reasoning output.

Open issues4

  • Issue#5892[Bug]: Native Anthropic extended-thinking not displayed by show_reasoning (content blocks not walked)
  • Issue#7251[Bug]: Telegram streaming hides reasoning even with display.show_reasoning enabled
  • Issue#7368[Feature]: Stream thinking/reasoning content on Telegram with collapsible blockquote
  • Issue#50193[Bug]: show_reasoning 💭 block never reaches Telegram — last_reasoning is None in gateway even though reasoning is stored in DB

Open PRs4

  • PR#7369feat(gateway): stream reasoning as collapsible blockquote on Telegram
  • PR#50609fix(gateway): reconcile previewed final responses
  • PR#57693fix(gateway): reasoning display is silently lost on every streamed turn
  • PR#93672fix(gateway): deliver the reasoning block when streaming already sent the body

1 PR closed without merging

From the close comments: other 1

  • #7433 fix(gateway): show reasoning on Telegram when streaming is enabled · other → 8a9bc38, #7433
Closed issues · 2
  • Closed#9685GatewayStreamConsumer._clean_for_display does not filter <think> blocks — reasoning content leaks to chat platforms during streaming
  • Closed#42008[Bug]: Reasoning/CoT silently dropped in gateway streaming mode — architectural gap
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.15: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Closed issues
2
Attempts
1 PR closed without merging

For your agent

The same facts, typed.