NousResearch/hermes-agent

Relay auxiliary requests decoded as chat completions versus Responses input

Cluster 137202 · agent. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #139050 on 15 Oct 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #139050. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #139050. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #139050, then check it covers your case.

Read #139050 Pick up a Lab task

Members appear to concern auxiliary calls through Relay, with two titles proposing to decode them as chat completions and one bug report citing an "OpenAI Responses request is missing input" error for MoA references on openai-codex. The cluster looks coherent around this boundary, but titles alone do not show the cause or outcome.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#139050 fix(agent): auxiliary Relay calls decode as chat completions (#137202, salvage #137203)

merged to main

files: agent/auxiliary_client.py, agent/auxiliary_hooks.py, agent/auxiliary_wire.py, contributors/emails/[redacted:email], tests/agent/test_auxiliary_hooks.py, tests/agent/test_auxiliary_relay.py

1 PR closed without merging

From the close comments: merged via another change 1

#137203 fix(agent): decode auxiliary Relay requests as chat completions · merged via another change → 12a3342, cdfa0ff, 9a77317, #139050, #137202, #138611

Closed issues · 1

Closed#137202[Bug]: MoA references on openai-codex fail at the Relay boundary: "OpenAI Responses request is missing input"

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
Merged PRs: #139050
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 15 Oct 2026

For your agent

The same facts, typed.

cluster/137202.json
cluster/137202.md