bug: insert mode accepts neovim commands in normal buffer

[dmtrKovalenko]

Prerequisites

• I searched the docs
• I searched existing issues

:checkhealth opencode output

opencode.nvim ~

• OS: Darwin 25.5.0 (arm64)
• nvim version: 0.12.0+v0.12.0.
• opencode.nvim git commit hash: 49ddecd84071ff52576bdadf62fc3707e78f552f.
• vim.g.opencode_opts: {
  server = {
  start = <function 1>
  }
  }

opencode.nvim [binaries] ~

• ✅ OK opencode available with version 1.17.6.
• ✅ OK curl available.
• ✅ OK pgrep available.
• ✅ OK lsof available.

opencode.nvim [snacks] ~

• ⚠️ WARNING snacks.input is disabled: ask() will not be enhanced.
• ✅ OK snacks.picker is enabled: select() will be enhanced.

Describe the bug

after the latest update when I type to the winodw it is closing cause some leader (space) based keys are handled

and also every space now is very slow

Screen.Recording.2026-06-13.at.21.42.48.mov

Steps To Reproduce

just type something

Expected Behavior

typing into opencode in insert mode should not activate any other bindings and close the input (o in my case toggles opencode)

[nickjvandyke]

The plugin has never set any <leader> keymaps, so I'm not sure why an update would cause this. But check your user-defined keymaps for one that's active in Terminal mode and uses <leader>. To fix it, either use a non-leader keymap, or remove Terminal mode from the mapping.

Reference the updated snacks.terminal example too https://github.com/nickjvandyke/opencode.nvim#server

[dmtrKovalenko]

argh I am so angry rn, your new suggested way of doing toggle is bindings on the "t" which is closing the instance when you type <space>o - I understand that you use the other kebindings, but this doesn't mean that other people setups have to be broken

[nickjvandyke]

So remove terminal mode from your keymap. It's merely a suggestion. The keymap that you choose, and the way Neovim handles it, is out of my control.