Repository navigation
Conversation
|
The following comment was made by an LLM, it may be inaccurate: |
![opencode-agent[bot]](https://avatars.githubusercontent.com/in/1549082?s=60&v=4){kind=small}
There was a problem hiding this comment.
Looks good. The right/left defaults on session.child.next/session.child.previous were never wired to a registered command, so setting them to none removes dead bindings without taking away any working navigation. It follows the existing pattern for retired keybinds (diff.toggle, session.share).
I ran the #56153 reproduction against both the base and this branch. In a child session with the subagent picker open, right only switches the picker tab on both, as expected. The difference shows up in the resolved config, not on screen. bun test test/config-v2.test.tsx (21 pass) and bun run typecheck in packages/tui both pass.
Public API: the config defaults for the keybind IDs session.child.next and session.child.previous change from right/left to none. Both IDs are still accepted in config, so existing configs keep loading. This is backwards compatible.
Related: #56154
Issue for this PR
Closes #56153
Type of change
What does this PR do?
Disable the unused
session.child.next/session.child.previousdefaults and mark them deprecated. Their configuration names remain accepted for compatibility, following the existing retired-keybind pattern. Child sessions use the subagent picker, whose arrows switch composer tabs.How did you verify your code works?
bun typecheckinpackages/tui,git diff --check, and the normal pre-pushbun run checkpassed (35/35 tasks).Screenshots / recordings
Configuration cleanup; no rendered UI changes.
Checklist
Added by the opencode bot (AI-generated).
Related: #56154
Public API: config defaults for keybinds session.child.next/previous change right/left → none; IDs still accepted (backwards compatible)