-
-
Notifications
You must be signed in to change notification settings - Fork 77
Description
Did you check docs and existing issues?
- I have read the plugin docs
- I have read the opencode docs
- I have searched the existing plugin issues
- I have searched the existing opencode issues
:checkhealth opencode output
============================================================================== opencode: 2 nvim version: 0.11.5. - opencode.nvim git commit hash: 0f85a4446720263b172521caa9cfaaf782a4f4ad. - vim.g.opencode_opts: { provider = { enabled = "tmux", tmux = { options = "-h -p 35" } } } opencode.nvim [binaries] ~ - ✅ OK opencode available with version 1.1.30. - ✅ OK curl available. - ✅ OK pgrep available. - ✅ OK lsof available. opencode.nvim [snacks] ~ - ✅ OK snacks.input is enabled: ask() will be enhanced. - ✅ OK snacks.picker is enabled: select() will be enhanced. opencode.nvim [providers] ~ - ✅ OK Configured opencode provider: tmux. - ✅ OK The snacks provider is available. - kitty provider is not available — KITTY_LISTEN_ON environment variable is not set. - ADVICE: - Enable remote control in kitty. - wezterm provider is not available — wezterm executable not found in $PATH. - ADVICE: - Install wezterm and ensure it's in your $PATH. - ✅ OK The tmux provider is available. - ✅ OK The terminal provider is available.
Describe the bug
When I trigger openning an opencode: plugin started to do wierd things. It switches to Insert mode and "type" sequence of chars right at the buffer. Please see screenshot:
That started to appear a week ago - previosly it was just fine.
P.S. And thank you for the plugin!!!
Steps To Reproduce
Trigger openning of opencode at tmux provider.
Observe sideeffect
Expected Behavior
No such weird behavior