Cairn
NousResearch/hermes-agent

Persist streaming responses on disconnect or cancellation

Cluster 15026 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

0open issues
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
0 issues and 1 PR.

These issues and fixes address a bug where in-progress or partial streaming responses are not saved when a client disconnects or a request is cancelled, and implement recovery mechanisms for background response runs.

Open issues0

No open issues.

Open PRs1

  • PR#15492fix(api-server): Implement background response run recovery

1 PR closed without merging

From the close comments: merged via another change 1

  • #15171 fix(api-server): persist response snapshot on client disconnect when store=True · merged via another change → a29bad2, #15392
Closed issues · 1
  • Closed#15026[Bug]: Streaming /v1/responses cannot be recovered after client disconnect because partial/in-progress responses are not persisted
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
gateway
Closed issues
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/15026.json
cluster/15026.md