Cairn
NousResearch/hermes-agent

MOA internal request field leaking to native client

Cluster 78382 · agent. Data as of

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

The short answer

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

These issues and fixes concern a private MOA field (_moa_prepared_request) leaking through to the native OpenAI client during fallback, rotation, or client rebuilds. The work involves stripping the field before dispatch and preserving the facade across client replacements.

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.

  • #83088 fix(agent): preserve MoA facade when rebuilding primary client (stream retry, rotation, fallback+restore)

    merged to main

    files: agent/agent_runtime_helpers.py, agent/chat_completion_helpers.py, agent/conversation_loop.py, contributors/emails/[redacted:email], run_agent.py, tests/agent/test_moa_prepared_request_client_swap.py, tests/run_agent/test_moa_loop_mode.py, tests/test_moa_prepared_request_leak_78382.py

2 PRs closed without merging

From the close comments: merged via another change 2

  • #78409 fix(moa): preserve facade across client rebuilds · merged via another change → #83088
  • #80132 fix(agent): strip _moa_prepared_request before dispatching to native client (#78382) · merged via another change → #83088
Closed issues · 1
  • Closed#78382MOA: _moa_prepared_request leaked to native OpenAI client when agent.client is replaced (fallback/rotation)
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.50: 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
#83088
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
15 Aug 2026

For your agent

The same facts, typed.

cluster/78382.json
cluster/78382.md