Double Ctrl+C during MCP shutdown leaking KeyboardInterrupt traceback
Cluster 39367 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #39479 on 5 Jun 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #39479. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #39479. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Members concern a second Ctrl+C during MCP shutdown in the CLI producing a KeyboardInterrupt traceback. Three are pull requests proposing to catch BaseException in shutdown guards, and one is an issue describing the behavior; none of this indicates whether the change was merged or works.
Open issues0
Open PRs0
Fixes on record
-
#39479 fix: catch BaseException in MCP shutdown guards to suppress double-Ctrl+C traceback
files:
cli.py,scripts/release.py,tools/mcp_tool.py
2 PRs closed without merging
From the close comments: merged via another change 1 · other 1
Closed issues · 1
- Closed#39367CLI: 2nd Ctrl+C during MCP shutdown escapes cleanup → KeyboardInterrupt traceback on exit
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- hermes cli
- Merged PRs
- #39479
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 5 Jun 2026