NousResearch/hermes-agent

MCP stdio watchdog interfering with uvx and launcher-based servers

Cluster 66423. Data as of

Nothing open on GitHub. Fix merged in #66858 on 18 Jul 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #66858. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #66858. That is separate from the fix event.
Still open
Nothing open on GitHub.

The members concern the MCP stdio watchdog and its handling of live servers, especially those started through launcher commands like uvx. One reports a bug where connections close after the handshake, and the others propose different approaches: using direct parent identity, skipping watchdog wrapping for launchers, or adding a disable option.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #66858 fix(mcp): use direct parent identity in watchdogs — stop false-killing live stdio servers (#62505, #66518, #66423)

    merged to main

    files: contributors/emails/[redacted:email], tests/test_slash_worker_watchdog.py, tests/tools/test_mcp_stdio_watchdog.py, tools/mcp_stdio_watchdog.py, tools/mcp_tool.py, tui_gateway/slash_worker.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #66430 fix(mcp): skip watchdog wrapping for launcher commands (uvx, npx, etc.) (#66423) · other → #66858, #66423
  • #66805 fix(mcp): add disable_watchdog config option for uvx servers (#66423) · done elsewhere → #66858
Closed issues · 1
  • Closed#66423[Bug]: mcp_stdio_watchdog breaks uvx-based MCP servers — "Connection closed" after handshake
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.00 means 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 Lab

At a glance

Merged PRs
#66858
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
18 Jul 2026

For your agent

The same facts, typed.