Skip to content

Reasoning-model thinking (type:"thinking") never rendered on Discord — /reasoning on shows no thoughts #94936

Description

@Marvinthebored

Summary

On Discord, a reasoning model's thinking is never presented to the user. With /reasoning on — which should surface the model's thinking as persistent messages — the thinking lane is dropped entirely: the thoughts are produced by the model and archived in the session, but no thinking content reaches the channel. Only the final answer is shown.

Environment

  • OpenClaw 2026.6.8 (production)
  • Provider/model: deepseek/deepseek-v4-flash (a reasoning model that reliably emits reasoning_content)
  • Flags: /think high, /verbose off, /reasoning on

Steps to reproduce

  1. /model deepseek/deepseek-v4-flash, then /think high, /verbose off, /reasoning on
  2. Send a prompt that induces reasoning plus a tool call, e.g. "Reason it through first, then use a tool to list your working directory and tell me the single largest file."
  3. Observe the Discord output.

Expected

With /reasoning on, the model's thinking should appear as persistent message(s), visually distinct from the final answer.

Actual

No thinking is shown at any point. During streaming the draft shows tool activity ephemerally, then collapses to the final answer only. The thinking is confirmed present in the session archive (multiple type:"thinking" parts per turn, ~100–195 characters each) but is never rendered.

Notes

  • Discord has no per-message thinking-stream mode (unlike Telegram's /reasoning stream), so under /reasoning on there is currently no path that surfaces thinking on Discord at all.
  • Reproduced with deepseek as a clean, reliable emitter; the gap affects reasoning models generally.
  • Screen recordings of the before-state are available and can be attached.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.no-staleExclude from stale automation

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions