You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ctrl+_ keybind (sent by pressing ctrl+/) used to work in 0.15.31 but no longer works in 1.0.16. Example:
"keybinds": {
"model_list": "ctrl+_",
}
Note that when you press ctrl+/, VS Code terminals send ctrl+_ (which gpt5 says is "more correct" 🤷) but iTerm2 sends ctrl+/. So YMMV depending on terminal.
If you want to change iTerm2 to instead send ctrl+_: Settings → Keys → Key Bindings → plus icon → "Send Hex Codes: 0x1F"
While none of these specifically address ctrl+_ (ctrl+/), they represent a broader pattern of keybinding regressions in v1.0 that might share the same underlying cause.
These keybinds are not working on 1.0.19.
Does anyone can verified these keybinds are working? @thdxr@jdanbrown
{
"$schema": "https://opencode.ai/config.json",
"keybinds": {
"input_submit": "ctrl+enter",
"input_newline": "enter",
}
}
It looks like enter was changed to return, so input_newline works fine.
But input_submit doesn’t work when I bind it to ctrl+return.
I’m guessing ctrl+return is already bound to something else.
So I changed the terminal keybind for ctrl+return to act as ctrl+p, and now everything works the way I want.
Activity
github-actions commentedon Nov 3, 2025
This issue might be related to other keybinding problems introduced in version 1.0. Please check:
While none of these specifically address ctrl+_ (ctrl+/), they represent a broader pattern of keybinding regressions in v1.0 that might share the same underlying cause.
thdxr commentedon Nov 3, 2025
fixed will release soon
jdanbrown commentedon Nov 3, 2025
Verified it's working in 1.0.18, thank you!
JSCOP commentedon Nov 4, 2025
These keybinds are not working on 1.0.19.
Does anyone can verified these keybinds are working?
@thdxr @jdanbrown
{
"$schema": "https://opencode.ai/config.json",
"keybinds": {
"input_submit": "ctrl+enter",
"input_newline": "enter",
}
}
rekram1-node commentedon Nov 4, 2025
@JSCOP we have a separate issue tracking newline behaviors
JSCOP commentedon Nov 4, 2025
@rekram1-node 1.0.20 doesn't work either please fix this please
rekram1-node commentedon Nov 4, 2025
@JSCOP what doesn't work? are we talking about newline still? Like I said for that, separate issue and we are going to fix it
JSCOP commentedon Nov 6, 2025
@rekram1-node
I found the reason why the keybinds weren’t working.
"keybinds": {
"input_newline": "return",
"input_submit": "ctrl+p"
}
It looks like enter was changed to return, so input_newline works fine.
But input_submit doesn’t work when I bind it to ctrl+return.
I’m guessing ctrl+return is already bound to something else.
So I changed the terminal keybind for ctrl+return to act as ctrl+p, and now everything works the way I want.
rekram1-node commentedon Nov 6, 2025
interesting, thanks for clarifying