Cairn

MCP interrupt cause reporting in tool loop

NousResearch/hermes-agent · cluster 133539 · mcp

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

All three members concern how MCP interrupts are reported, in particular an InterruptedError that says "User sent a new message" even for system interrupts. Two titles describe changes to preserve or render the recorded interrupt cause instead of a hardcoded message, and one describes the underlying issue.

Open issues1

  • Issue#133539MCP tool loop raises InterruptedError("User sent a new message") for system interrupts too

Open PRs2

  • PR#133547fix(mcp): render the recorded interrupt cause, not a hardcoded user message
  • PR#138202fix(mcp): preserve MCP interrupt causes
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.67: 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

Subsystem
mcp
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/133539.json
cluster/133539.md