NousResearch/hermes-agent

ACP crashes when stdout is not a pipe

Cluster 84515 · acp. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs 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 0 PRs.

These members address a bug where the Hermes ACP crashes with a 'Pipe transport is only for pipes' error when stdout is not pipe-backed, along with proposed fixes to bridge or pump stdio in that scenario.

Open issues1

  • Issue#84515[Bug]: hermes acp crashes with 'Pipe transport is only for pipes' when stdout is not a pipe

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · stale or abandoned 1

  • #84540 fix(acp): bridge non-pipe stdout for ACP SDK connect_write_pipe · duplicate → #84564
  • #84564 fix(acp): pump stdio when stdout is not pipe-backed (#84515) · stale or abandoned
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
acp
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.