NousResearch/hermes-agent
Reasoning details routing fixes for OpenRouter upstreams
Cluster 129037 · agent. 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 address how reasoning/replay details are handled when routing through OpenRouter, including gating replay on provider support and stripping or allowlisting reasoning_details fields to avoid upstream errors.
Open issues1
- Issue#129037reasoning_details allowlist keys on transit host, not resolved upstream: OpenRouter→strict-upstream funnel still 400s (openrouter.ai branch of _route_replays_reasoning_details)
Open PRs1
- PR#129043fix(agent): gate reasoning replay on upstream provider
1 PR closed without merging
From the close comments: superseded by another PR 1
- #129400 fix(transports): strip reasoning_details for Gemini/Gemma upstreams on OpenRouter (#129037) · superseded by another PR
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
- agent
- Closed issues
- 0
- Attempts
- 1 PR closed without merging