Cairn

Add text verbosity config for OpenAI Responses API

NousResearch/hermes-agent · cluster 20203 · agent

Data as of

Nothing open on GitHub. Fix merged in #115880. Check it covers your case.

The short answer

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

These items concern adding an agent.text_verbosity configuration option to control response length verbosity when using the OpenAI Responses API, targeting GPT-5 and later models. The work spans feature requests and implementation across the OpenAI and Codex layers.

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.

  • #115880 feat(openai): agent.text_verbosity controls Responses answer length (#20203, salvage #20258)

    merged to main

    files: agent/agent_init.py, agent/chat_completion_helpers.py, agent/codex_responses_adapter.py, agent/transports/codex.py, contributors/emails/[redacted:email], hermes_cli/config_defaults.py, tests/agent/test_codex_responses_adapter.py, tests/agent/transports/test_codex_transport.py, website/docs/user-guide/configuration.md

3 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1 · other 1

  • #29574 feat(openai): support Responses text verbosity · other → 44d3b1b
  • #59844 feat(codex): add agent.text_verbosity config for GPT-5+ response length control · superseded by another PR → #115880
  • #72638 feat(openai): configure Responses verbosity · done elsewhere → 1285de7, #115880
Closed issues · 1
  • Closed#20203[Feature]: Add configuration support for OpenAI Responses API text verbosity
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.40: 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
#115880
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
19 Sep 2026

For your agent

The same facts, typed.

cluster/20203.json
cluster/20203.md