MCP server processes not killed on CLI exit
- Vorherrschende Sprache
- Shell
- Sterne
- 11.2k
- Forks
- 1.9k
- Ø Merge
- 14 Std. 16 Min.
- Gemergte PRs (30 T.)
- 6
Beschreibung
### Describe the bug
_No response_
### Affected version
_No response_
### Steps to reproduce the behavior
Body: After exiting copilot, ssh-mcp (and other MCP) child processes remain alive in Activity Monitor. Each
consumes ~tens of MB. Expected behavior: CLI should send SIGTERM to all spawned MCP child processes on exit.
Steps to reproduce: 1. Start copilot with SSH MCP servers configured. 2. Exit with Ctrl+D or /exit. 3. Run
pgrep -la mcp — processes still alive.
### Expected behavior
_No response_
### Additional context
_No response_
Beitragsleitfaden
Rechercherichtung
Start by reproducing the issue from the copilot CLI with an SSH MCP server configured, exiting via Ctrl+D and /exit, then check the remaining processes with `pgrep -la mcp`. Trace the CLI entry point's shutdown and MCP child-process handling; done means all spawned MCP processes receive SIGTERM and no longer remain after exit.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- shell
- Bereich
- cli
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 52/100