Cairn
NousResearch/hermes-agent

OpenAI non-reasoning models rejecting Responses reasoning/include parameters

Cluster 23450 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

0open issues
3open PRs
9items grouped
Known?
Yes. 9 related items grouped here, 3 issues already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
0 issues and 3 PRs.

Members report HTTP 400 errors such as "Encrypted content is not supported with this model" when Hermes uses GPT-4o, GPT-4o-mini, or GPT-4.1. Related pull requests propose gating reasoning or include parameters, or choosing the API mode, based on model capability.

Open issues0

No open issues.

Open PRs3

  • PR#23460fix(transports/codex): remove unsupported include parameter for standard OpenAI Chat Completions API
  • PR#23734fix(agent): only upgrade to codex_responses for models that require it
  • PR#24234fix: only send reasoning.encrypted_content include for supported models

3 PRs closed without merging

From the close comments: closed without comment 1 · done elsewhere 1 · other 1

  • #46550 fix(agent): omit Responses reasoning param for non-reasoning OpenAI models · other → #46516
  • #47820 fix(openai): model-aware api_mode for direct api.openai.com (GPT-4.1/4o use Chat Completions) · done elsewhere → 77e2992, #23450, #76255, #23460, #24234, #23734
  • #52047 fix(codex): gate reasoning params on model capability (#52023) · closed without comment
Closed issues · 3
  • Closed#23450[Bug]: [Bug]: Hermes v0.13.0 sends unsupported `include` parameter causing "Encrypted content is not supported with this model" error with OpenAI GPT-4o
  • Closed#46516[Bug]: [OpenAI API] HTTP 400 for gpt-4.1 and gpt-4o-mini on Hermes 0.16.0 (Windows) while direct API calls work
  • Closed#52023[Bug]: GPT-4o-mini and GPT-4.1 (and more) fail with "Encrypted content is not supported with this model" after clean install
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.19: 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
3
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/23450.json
cluster/23450.md