-
Notifications
You must be signed in to change notification settings - Fork 4.9k
feat: add config option for sidebar default state #6955
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
Adds a new `tui.sidebar` config option to set the sidebar's initial state. Accepts "auto" (default), "show", or "hide". - Config provides initial default before user interaction - User toggles via keybind are stored in KV and take precedence - Priority: KV store > config.tui.sidebar > "auto" Closes anomalyco#3682
|
The following comment was made by an LLM, it may be inaccurate: SummaryNo duplicate PRs found. The search returned the PR itself (6955) but no other open PRs addressing the same feature. However, I found related PRs that might be worth reviewing for context:
These are not duplicates but may have overlapping concerns around sidebar state management and persistence that could benefit from coordination. |
Changes After Reviewing Related PRsAfter reviewing #6594, #6092, and #6093,the following issues were identified and fixed:
|
- Fix KV persistence bug in sidebar toggle handler - Add runtime validation for config values - Add documentation for sidebar config optionk
…ode into feat/tui-sidebar-config
|
Hey! Your PR title Please update it to start with one of:
See CONTRIBUTING.md for details. |
…ode into feat/tui-sidebar-config
# Conflicts: # packages/opencode/src/cli/cmd/tui/routes/session/index.tsx
Adds a new
tui.sidebarconfig option to set the sidebar's initial state. Accepts "auto" (default), "show", or "hide".Closes #3682