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

[FEATURE]: Hide thinking blocks with configuration toggle #7491

New Issue
Open
opened 2026-02-16 18:07:21 -05:00 by yindo · 5 comments
yindo commented 2026-02-16 18:07:21 -05:00
Owner
Copy Link
Copy Source

Originally created by @jpmelos on GitHub (Jan 24, 2026).

Originally assigned to: @thdxr 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

Currently, I have to type /thinking in every session to not see thinking blocks. It's annoying. I'm generally not interested in the flow of thinking blocks and I'd rather have a more concise view of things.

I would like to have a configuration toggle for this. I don't know whether this configuration should live in the TUI level or should be applied elsewhere, but I'm thinking something like (in opencode.json):

{
    "tui": {
        "show_thinking": true
    }
}

Default is true, to maintain backward-compatibility with current behavior.

If set, it will become the de-facto default for the installation and will override whatever is in the state file for this setting.

Thoughts?

Originally created by @jpmelos on GitHub (Jan 24, 2026). Originally assigned to: @thdxr 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 Currently, I have to type `/thinking` in every session to not see thinking blocks. It's annoying. I'm generally not interested in the flow of thinking blocks and I'd rather have a more concise view of things. I would like to have a configuration toggle for this. I don't know whether this configuration should live in the TUI level or should be applied elsewhere, but I'm thinking something like (in `opencode.json`): ```json { "tui": { "show_thinking": true } } ``` Default is `true`, to maintain backward-compatibility with current behavior. If set, it will become the de-facto default for the installation and will override whatever is in the state file for this setting. Thoughts?
yindo added the discussion label 2026-02-16 18:07:21 -05:00
yindo commented 2026-02-16 18:07:21 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 24, 2026):

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

  • #8167: [FEATURE]: keybind to toggle thinking visibility (/thinking) - requests a keybind shortcut for the same functionality
  • #7866: WebUI: thinking/reasoning blocks hidden after response completion, no way to show them - related to thinking visibility control in the UI

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 24, 2026): This issue might be a duplicate of existing issues. Please check: - #8167: [FEATURE]: keybind to toggle thinking visibility (/thinking) - requests a keybind shortcut for the same functionality - #7866: WebUI: thinking/reasoning blocks hidden after response completion, no way to show them - related to thinking visibility control in the UI Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 18:07:21 -05:00
Author
Owner
Copy Link
Copy Source

@jpmelos commented on GitHub (Jan 24, 2026):

This is not a duplicate of https://github.com/anomalyco/opencode/issues/8167, but certainly related. Definitely not a duplicate of https://github.com/anomalyco/opencode/issues/7866, which is related to thinking blocks in the WebUI not being shown at all.

@jpmelos commented on GitHub (Jan 24, 2026): This is not a duplicate of https://github.com/anomalyco/opencode/issues/8167, but certainly related. Definitely not a duplicate of https://github.com/anomalyco/opencode/issues/7866, which is related to thinking blocks in the WebUI not being shown at all.
yindo commented 2026-02-16 18:07:21 -05:00
Author
Owner
Copy Link
Copy Source

@jpmelos commented on GitHub (Jan 24, 2026):

Ignore, this is not true. There is a KV entry for this to persist it across sessions.

@jpmelos commented on GitHub (Jan 24, 2026): Ignore, this is not true. There is a KV entry for this to persist it across sessions.
yindo commented 2026-02-16 18:07:21 -05:00
Author
Owner
Copy Link
Copy Source

@jpmelos commented on GitHub (Jan 24, 2026):

Actually, this is still useful... I want to have this setting committed to my dotfiles repository, which is a public repository, and I believe the state file is not something that's supposed to be persisted like that, is it? The benefit of having this committed to my dotfiles is that it will still apply to new installations.

@jpmelos commented on GitHub (Jan 24, 2026): Actually, this is still useful... I want to have this setting committed to my dotfiles repository, which is a public repository, and I believe the state file is not something that's supposed to be persisted like that, is it? The benefit of having this committed to my dotfiles is that it will still apply to new installations.
yindo commented 2026-02-16 18:07:21 -05:00
Author
Owner
Copy Link
Copy Source

@surak commented on GitHub (Feb 16, 2026):

Ignore, this is not true. There is a KV entry for this to persist it across sessions.

how?

@surak commented on GitHub (Feb 16, 2026): > Ignore, this is not true. There is a KV entry for this to persist it across sessions. how?
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 discussion
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#7491
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?