Cairn
NousResearch/hermes-agent

Nested API response envelope unwrapping fixes

Cluster 63408 · agent. Data as of

2 open items. Fix merged in #131907 on 5 Oct 2026. Check it covers your case.

The short answer

0open issues
2open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #131907. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #131907. That is separate from the fix event.
Still open
0 issues and 2 PRs.

These issues and fixes concern custom or auxiliary API providers returning responses wrapped in an extra envelope (e.g., {"data": {...}}), which causes parsing failures. Multiple fixes address unwrapping these nested structures across agent and vision code paths.

Open issues0

No open issues.

Open PRs2

  • PR#63409fix(agent): unwrap data/success envelope in auxiliary LLM responses
  • PR#63541fix(auxiliary_client): unwrap custom provider response wrappers for vision

Fixes on record

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

  • #131907 fix(agent): unwrap data/success envelope in auxiliary LLM responses [risk 0.30]

    merged to main

    files: agent/auxiliary_client.py, contributors/emails/[redacted:email], tests/agent/test_auxiliary_client.py

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #66751 fix(agent): unwrap nested OpenAI-compat response envelopes · superseded by another PR → bb230bd, #63409, #66750, #63408
Closed issues · 2
  • Closed#63408Custom provider response wrapper {"data": {...}} not unwrapped — vision fails with empty ChatCompletion
  • Closed#66750[Bug]: custom api.cline.bot endpoint returns nested non-streaming envelope (choices=None)
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.36: 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
#131907
Closed issues
2
Attempts
1 PR closed without merging
Fix link checked
5 Oct 2026

For your agent

The same facts, typed.

cluster/63408.json
cluster/63408.md