NousResearch/hermes-agent
ACP sessions ignoring configured MCP call timeouts
Cluster 88213 · acp. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese items concern a bug where ACP sessions do not respect the configured MCP call timeout. The fixes aim to preserve or inherit that timeout setting for ACP-supplied servers.
Open issues1
- Issue#88213[Bug]: ACP sessions ignore configured MCP call timeouts
Open PRs1
- PR#88218fix(acp): inherit configured MCP call timeout
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#88230 fix(acp): preserve configured MCP call timeout for ACP-supplied servers · superseded by another PR →
#88218
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.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
- acp
- Closed issues
- 0
- Attempts
- 1 PR closed without merging