nhcarrigan/hikari-desktop
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 9 Pull Requests 36 Actions Releases 22 Activity

Support extended thinking blocks display #120

New Issue
Closed
opened 2026-02-06 16:31:10 -08:00 by hikari Β· 1 comment
hikari commented 2026-02-06 16:31:10 -08:00
Owner
Copy Link
Copy Source

Description

Claude Code supports extended thinking blocks where Claude shows its reasoning process. Multiple changelog versions reference improvements to thinking block handling.

Current State

We don't currently parse or display thinking blocks in the conversation view.

Proposed Changes

  1. Parse thinking content blocks from assistant messages
  2. Add a collapsible "Thinking" section in the conversation view
  3. Style thinking blocks distinctly from regular content (e.g., dimmed, italic)
  4. Consider a toggle to show/hide thinking blocks globally

References

  • Various changelog entries reference thinking block improvements
  • Thinking blocks appear as content blocks with type: "thinking" in assistant messages

Priority

Medium - Thinking blocks provide valuable insight into Claude's reasoning

✨ This issue was created with help from Hikari~ 🌸

## Description Claude Code supports extended thinking blocks where Claude shows its reasoning process. Multiple changelog versions reference improvements to thinking block handling. ## Current State We don't currently parse or display thinking blocks in the conversation view. ## Proposed Changes 1. Parse `thinking` content blocks from assistant messages 2. Add a collapsible "Thinking" section in the conversation view 3. Style thinking blocks distinctly from regular content (e.g., dimmed, italic) 4. Consider a toggle to show/hide thinking blocks globally ## References - Various changelog entries reference thinking block improvements - Thinking blocks appear as content blocks with `type: "thinking"` in assistant messages ## Priority Medium - Thinking blocks provide valuable insight into Claude's reasoning ✨ This issue was created with help from Hikari~ 🌸
hikari commented 2026-02-07 12:43:01 -08:00
Author
Owner
Copy Link
Copy Source

βœ… Implementation Complete (Awaiting CLI Support)

I've successfully implemented full support for extended thinking blocks display in commit 7781b2c! πŸŽ‰

What Was Implemented:

Backend (Rust):

  • βœ… Modified wsl_bridge.rs to emit thinking blocks with dedicated line_type: "thinking"
  • βœ… Sends raw thinking content (no [Thinking] prefix)

Frontend:

  • βœ… Added "thinking" to TerminalLine type union
  • βœ… Created ThinkingBlock.svelte component with collapsible UI
  • βœ… Updated Terminal.svelte to render thinking blocks conditionally
  • βœ… Added show_thinking_blocks config toggle (default: true)
  • βœ… Added UI toggle in Settings β†’ Appearance section

Component Features:

  • πŸ’‘ Lightbulb icon to indicate extended thinking
  • πŸ“… Timestamp display
  • ⬇️ Collapsible/expandable with animated chevron
  • 🎨 Distinct styling: dimmed, italic, monospace text
  • βš™οΈ Respects global config setting

Current Status: ⏳ Awaiting CLI Support

Extended thinking blocks are not currently being emitted by Claude Code CLI. Based on research:

  • Extended thinking is supported in Claude 4 models and Claude 3.7 Sonnet
  • There's an active GitHub issue (#287658) about enabling extended thinking in Claude Code
  • The feature appears to still be in development for the CLI

Testing:

Attempted to trigger extended thinking with various complex prompts (algorithmic analysis, multi-step reasoning, mathematical proofs), but no thinking blocks were received from the CLI. This suggests the feature isn't enabled yet in Claude Code.

Next Steps:

Our implementation is complete and ready! Once Claude Code CLI starts emitting thinking content blocks:

  • They will automatically display in the conversation
  • Users can toggle visibility via Settings
  • The collapsible UI will show Claude's reasoning process

The implementation is future-proof and awaiting upstream CLI support! 🌸

✨ Implemented by Hikari~ 🌸

## βœ… Implementation Complete (Awaiting CLI Support) I've successfully implemented full support for extended thinking blocks display in commit `7781b2c`! πŸŽ‰ ### What Was Implemented: **Backend (Rust)**: - βœ… Modified `wsl_bridge.rs` to emit thinking blocks with dedicated `line_type: "thinking"` - βœ… Sends raw thinking content (no `[Thinking]` prefix) **Frontend**: - βœ… Added "thinking" to `TerminalLine` type union - βœ… Created `ThinkingBlock.svelte` component with collapsible UI - βœ… Updated `Terminal.svelte` to render thinking blocks conditionally - βœ… Added `show_thinking_blocks` config toggle (default: true) - βœ… Added UI toggle in Settings β†’ Appearance section **Component Features**: - πŸ’‘ Lightbulb icon to indicate extended thinking - πŸ“… Timestamp display - ⬇️ Collapsible/expandable with animated chevron - 🎨 Distinct styling: dimmed, italic, monospace text - βš™οΈ Respects global config setting ### Current Status: ⏳ Awaiting CLI Support Extended thinking blocks are **not currently being emitted** by Claude Code CLI. Based on research: - Extended thinking is supported in Claude 4 models and Claude 3.7 Sonnet - There's an active [GitHub issue (#287658)](https://github.com/microsoft/vscode/issues/287658) about enabling extended thinking in Claude Code - The feature appears to still be in development for the CLI ### Testing: Attempted to trigger extended thinking with various complex prompts (algorithmic analysis, multi-step reasoning, mathematical proofs), but **no thinking blocks were received** from the CLI. This suggests the feature isn't enabled yet in Claude Code. ### Next Steps: Our implementation is **complete and ready**! Once Claude Code CLI starts emitting thinking content blocks: - They will automatically display in the conversation - Users can toggle visibility via Settings - The collapsible UI will show Claude's reasoning process The implementation is future-proof and awaiting upstream CLI support! 🌸 ✨ Implemented by Hikari~ 🌸
naomi closed this issue 2026-03-06 23:49:06 -08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/hikari-desktop#120
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?