Replies: 2 comments 2 replies
-
|
Possible cause: Killing the process with SIGKILL prevents it from graceful shutdown (forwarding the signal to the child processes, etc.). I see the same issue with agents installed via Volta, which runs node app as its child process. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
https://github.com/neovim/neovim/issues/39552?utm_source=chatgpt.com might be a related, the codex-acp is installed through npm while it's a rust binary, if you install it from source with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
hello, I'm just wondering if there could be an issue with closing acp adapters, in particular codex-acp, let me try to explain:
if you open a chat, select codex then entirely close neovim, the codex-acp binary still pops up running:
when using claude, I wasnt able to reproduce. I wasnt also with copilot acp
so could this be a codecompanion issue or maybe a codex-acp one since it seems to appear just with codex but I wasnt able to find something interesting in their issues.. ?
Beta Was this translation helpful? Give feedback.
All reactions