After the neovim process ends, the `opencode serve` process does not close accordingly

[widdsun]

Every time I open and close neovim, an opencode serve process spawned by this plugin is left running, which causes excessive memory usage. It seems the only solution is to manually terminate the opencode serve process.
I'm not sure if this is intented behavior or a bug. Can the same opencode serve be reused by multiple neovim instances?

[sudo-tee]

Thanks for the report.

This is a puzzling issue as it does not happen to everyone and I am not able to reproduce it yet

I will have another look

I might need some help debugging it.

[sudo-tee]

@widdsun

I played with the shutdown of the server in a PR, please let me know if it resolves the issue for you. As I was not experiencing this issue

#255

[pirey]

@sudo-tee while I tried the branch, I found out this particular issue still persists

the opencode serve process was not killed after exit, and opening neovim will spawn another process.

Screen.Recording.2026-02-10.at.08.28.34.mp4

[sudo-tee]

What OS are you using?

Do you have a link to your dotfiles ?

I seriously don't know why it's happening but only for few people

[pirey]

I am using macos running neovim nightly release.
here's my dotfiles and neovim config
https://github.com/pirey/dotfiles/tree/master/config-files/home
https://github.com/pirey/nvim

[sudo-tee]

@pirey @widdsun

I simplified the shutdown logic to the minimum and added some logging

you can enable it in your config

{
   logging {
      enabled = true,
      level = 'debug'
   }
}

Could you do me a favor and enable the log even if it works for you so I can see if there is an error in one of the SIGTERM or SIGKILL ?

file path should be ~/.local/state/nvim/opencode.log

Thank you very much

[pirey]

I found something. @sudo-tee

I tried to monitor the spawned opencode process (using btop), and apparently the spawned process had a child process.
And when I exit neovim, the cleanup function only kill the parent process, leaving the child process orphaned.

Screen.Recording.2026-02-10.at.21.33.34.mov

Here's a screenshot with the full command

[pirey]

Here's the log file that you mentioned.
I cleared some earlier logs, though. I opened and close neovim and opencode several times after that.

[DEBUG Tue Feb 10 21:33:12 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: spawn: started job with pid=36186
[DEBUG Tue Feb 10 21:33:13 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: spawn: server ready at url=http://127.0.0.1:4096
[DEBUG Tue Feb 10 21:33:18 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: shutdown: SIGTERM pid=36186 ok=true err=0
[DEBUG Tue Feb 10 21:33:18 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: shutdown: SIGKILL pid=36186 ok=true err=0
[DEBUG Tue Feb 10 21:33:39 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: spawn: started job with pid=36369
[DEBUG Tue Feb 10 21:33:39 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: spawn: server ready at url=http://127.0.0.1:4096
[DEBUG Tue Feb 10 21:33:44 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: shutdown: SIGTERM pid=36369 ok=true err=0
[DEBUG Tue Feb 10 21:33:44 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: shutdown: SIGKILL pid=36369 ok=true err=0
[DEBUG Tue Feb 10 21:37:04 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: spawn: started job with pid=36550
[DEBUG Tue Feb 10 21:37:04 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: spawn: server ready at url=http://127.0.0.1:51687
[DEBUG Tue Feb 10 21:37:07 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: shutdown: SIGTERM pid=36550 ok=true err=0
[DEBUG Tue Feb 10 21:37:07 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: shutdown: SIGKILL pid=36550 ok=true err=0
[DEBUG Tue Feb 10 21:37:11 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: spawn: started job with pid=36697
[DEBUG Tue Feb 10 21:37:11 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: spawn: server ready at url=http://127.0.0.1:51733
[DEBUG Tue Feb 10 21:37:13 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: shutdown: SIGTERM pid=36697 ok=true err=0
[DEBUG Tue Feb 10 21:37:13 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: shutdown: SIGKILL pid=36697 ok=true err=0
[DEBUG Tue Feb 10 21:37:49 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: spawn: started job with pid=36920
[DEBUG Tue Feb 10 21:37:50 2026] /Users/yeri/.local/share/nvim/site/pack/core/opt/opencode.nvim/lua/opencode/log.lua:22: spawn: server ready at url=http://127.0.0.1:4096

[sudo-tee]

@pirey

Thanks for the clarification.

I added a check for child process before killing it.

Let me know it it works properly for you now

[pirey]

Hey thanks.

I can confirm that the spawned process and its child has been terminated now.

Works well on my end.

Screen.Recording.2026-02-10.at.23.33.10.mov

[sudo-tee]

Awesome it looks like it solves your other issue at the same time.

I will merge this :)