anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Show thinking/reasoning indicator near input box when thinking is hidden #8460

New Issue
Open
opened 2026-02-16 18:10:01 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:10:01 -05:00
Owner
Copy Link
Copy Source

Originally created by @rcdailey on GitHub (Feb 3, 2026).

Originally assigned to: @rekram1-node on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

When using the /thinking command to hide thinking blocks (or with a future config toggle per #10470), there's no visual feedback that the model is actively reasoning. The TUI appears idle/hung, leaving users uncertain whether something is happening.

Request: Add a visual indicator (e.g., "Thinking..." text, spinner, or icon) near the chat input box (above or below it) that appears when:

  1. The model is in a thinking/reasoning phase
  2. Thinking visibility is toggled off

This differs from #9655 (sidebar status) and #7093 (general "waiting for" indicator) because:

  • It specifically targets the thinking/reasoning phase, not general LLM streaming or tool execution
  • It's positioned near the input box rather than the sidebar, which many users don't have visible
  • It only activates when thinking output is hidden, so users who see the thinking stream already have feedback

Why this matters:

  • Extended thinking models (Claude with thinking, DeepSeek reasoner, etc.) can spend significant time in the reasoning phase before producing visible output
  • When thinking is hidden to reduce clutter, users lose the visual feedback that reasoning text provides
  • Without an indicator, it's indistinguishable from a hung connection or stalled request

Suggested implementation:

  • Small status text or animated indicator in the input area footer (where the current bouncing animation lives)
  • Only shown when: (a) model is in thinking phase AND (b) thinking visibility is off
  • Could show elapsed time to set expectations for longer reasoning tasks
Originally created by @rcdailey on GitHub (Feb 3, 2026). Originally assigned to: @rekram1-node on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request When using the `/thinking` command to hide thinking blocks (or with a future config toggle per #10470), there's no visual feedback that the model is actively reasoning. The TUI appears idle/hung, leaving users uncertain whether something is happening. **Request:** Add a visual indicator (e.g., "Thinking..." text, spinner, or icon) near the chat input box (above or below it) that appears when: 1. The model is in a thinking/reasoning phase 2. Thinking visibility is toggled off This differs from #9655 (sidebar status) and #7093 (general "waiting for" indicator) because: - It specifically targets the thinking/reasoning phase, not general LLM streaming or tool execution - It's positioned near the input box rather than the sidebar, which many users don't have visible - It only activates when thinking output is hidden, so users who see the thinking stream already have feedback **Why this matters:** - Extended thinking models (Claude with thinking, DeepSeek reasoner, etc.) can spend significant time in the reasoning phase before producing visible output - When thinking is hidden to reduce clutter, users lose the visual feedback that reasoning text provides - Without an indicator, it's indistinguishable from a hung connection or stalled request **Suggested implementation:** - Small status text or animated indicator in the input area footer (where the current bouncing animation lives) - Only shown when: (a) model is in thinking phase AND (b) thinking visibility is off - Could show elapsed time to set expectations for longer reasoning tasks
yindo commented 2026-02-16 18:10:02 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 3, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #10470: [FEATURE]: Hide thinking blocks with configuration toggle - requests ability to toggle thinking visibility globally
  • #8789: [BUG/FEATURE]: Desktop GUI - Thinking process disappears and cannot be viewed in detail - reports thinking visibility issues in Desktop GUI
  • #7866: WebUI: thinking/reasoning blocks hidden after response completion, no way to show them - directly addresses hidden thinking blocks in WebUI

These issues discuss the thinking visibility problem that your feature request aims to solve. While your feature specifically targets a visual indicator when thinking is hidden (rather than showing the thinking itself), these related discussions may have additional context.

Feel free to ignore if your feature request addresses a specific gap not covered by these issues.

@github-actions[bot] commented on GitHub (Feb 3, 2026): This issue might be a duplicate of existing issues. Please check: - #10470: [FEATURE]: Hide thinking blocks with configuration toggle - requests ability to toggle thinking visibility globally - #8789: [BUG/FEATURE]: Desktop GUI - Thinking process disappears and cannot be viewed in detail - reports thinking visibility issues in Desktop GUI - #7866: WebUI: thinking/reasoning blocks hidden after response completion, no way to show them - directly addresses hidden thinking blocks in WebUI These issues discuss the thinking visibility problem that your feature request aims to solve. While your feature specifically targets a visual indicator when thinking is hidden (rather than showing the thinking itself), these related discussions may have additional context. Feel free to ignore if your feature request addresses a specific gap not covered by these issues.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8460
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?