Did you check docs and existing issues?
Neovim version (nvim -v)
all
Operating system/version
all
Describe the bug
In the example below, I have the mux option disabled, but I'm running Neovim inside tmux.
Then after opening opencode in a Neovim terminal, there will be three ways for sidekick to communicate with the running opencode process:
- the Neovim terminal
- we can use
tmux paste-buffer
- we can attach to the opencode http server started by the process
While technically, this is all correct, it's also confusing and we should be able to
detect that these are all in fact the same running process and only show one session.
Which session to show should be based on priorities, where in this case terminal > opencode_server > tmux.
Steps To Reproduce
opts.cli.mux.enabled = false
- start a tmux session
- start nvim
- toggle
opencode with sidekick
Expected Behavior
only one session
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()
require("lazy.minit").repro({
spec = {
{ "folke/sidekick.nvim", opts = {} },
-- add any other plugins here
},
})
Did you check docs and existing issues?
Neovim version (nvim -v)
all
Operating system/version
all
Describe the bug
In the example below, I have the
muxoption disabled, but I'm running Neovim inside tmux.Then after opening
opencodein a Neovim terminal, there will be three ways for sidekick to communicate with the running opencode process:tmux paste-bufferWhile technically, this is all correct, it's also confusing and we should be able to
detect that these are all in fact the same running process and only show one session.
Which session to show should be based on priorities, where in this case
terminal > opencode_server > tmux.Steps To Reproduce
opts.cli.mux.enabled = falseopencodewith sidekickExpected Behavior
only one session
Repro