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

Improve consistency/clarity by moving the remaining session-agnostic KV-persisted toggles to the System category #9223

New Issue
Open
opened 2026-02-16 18:11:56 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:11:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @ariane-emory on GitHub (Feb 12, 2026).

Originally assigned to: @thdxr on GitHub.

Description

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

At this point in time, some of the items in the command palette the toggle the states of options related to hiding or showing elements or changing their appearance, that are persistent to the kv.json file, and that persist across sessions live in the System subgroup of the command palette while some live in the the Session subgroup:

Items that are already in the System group

  • Disable/Enable animations
  • Disable/Enable diff wrapping
  • Toggle appearance

Items that languish in the Session group

  • Show/Hide timestamps
  • Show/Hide thinking
  • Show/Hide tool details
  • Show/Hide header

For consistency and clarity, the items that are currently located in the session group ought be moved to the system group for these reasons:

  • Their current placement is deceptive: none of these options relate to or affect the current session specifically, and as they are persisted to the KV file, their state persists through session boundaries (such as the execution of a /new command or a restart of OpenCode).
  • In the vast majority of cases, consistency is preferable to inconsistency.

My conclusion:

To achieve consistency and gain clarity, these four items listed above that are located in the Session group ought to be moved to the System group, and ought to be available for use before sending a message and beginning a session.

Plugins

No response

OpenCode version

1.1.64+ (HEAD of dev)

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Originally created by @ariane-emory on GitHub (Feb 12, 2026). Originally assigned to: @thdxr on GitHub. ### Description ### 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 At this point in time, some of the items in the command palette the toggle the states of options related to hiding or showing elements or changing their appearance, that are persistent to the `kv.json` file, and that persist across sessions live in the `System` subgroup of the command palette while some live in the the `Session` subgroup: #### Items that are already in the System group - Disable/Enable animations - Disable/Enable diff wrapping - Toggle appearance #### Items that languish in the Session group - Show/Hide timestamps - Show/Hide thinking - Show/Hide tool details - Show/Hide header For consistency and clarity, the items that are currently located in the session group ought be moved to the system group for these reasons: - Their current placement is deceptive: none of these options relate to or affect the current session specifically, and as they are persisted to the KV file, their state persists through session boundaries (such as the execution of a `/new` command or a restart of OpenCode). - In the vast majority of cases, consistency is preferable to inconsistency. ### My conclusion: To achieve consistency and gain clarity, these four items listed above that are located in the Session group ought to be moved to the System group, and ought to be available for use before sending a message and beginning a session. ### Plugins _No response_ ### OpenCode version 1.1.64+ (HEAD of dev) ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System _No response_ ### Terminal _No response_
yindo added the bug label 2026-02-16 18:11:56 -05:00
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 bug
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#9223
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?