Cairn

Gateway extra_body handling across primary and fallback provider routes

NousResearch/hermes-agent · cluster 136554 · agent

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.

These items concern how a cached gateway agent's extra_body is handled when it is on a fallback provider versus the primary route, including a report of the primary route's extra_body being re-applied during turn merge. Two members appear to be fix proposals touching gateway and agent code, one mentioning ownership tracking across routes and restore; their outcomes are not stated in the titles.

Open issues1

  • Issue#136554Gateway turn merge re-applies the primary route's extra_body to a cached agent that is still on its fallback provider

Open PRs2

  • PR#136564fix(gateway): keep fallback extra_body on cached agents with gated re…
  • PR#139367fix(agent): track custom-provider extra_body ownership across routes and restore
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
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/136554.json
cluster/136554.md