Cairn
NousResearch/hermes-agent

Configurable endpoint and credentials for OpenAI image generation

Cluster 65309 · agent. Data as of

Nothing open on GitHub. Fix merged in #115803 on 19 Sep 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 #115803. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #115803. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items cover adding support for custom base URLs, API key environment variable configuration, and credential routing in the OpenAI image generation config. The changes allow users to specify endpoint and credential sources via config.yaml.

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.

  • #115803 feat(image_gen): OpenAI image provider honours image_gen.openai.base_url/key_env, no project-header 403, no macOS system-proxy detour (#65309, #97928, #13798, #60748, #64888, salvage #65312 #64893 #60749)

    merged to main

    files: agent/video_gen_provider.py, plugins/image_gen/_common.py, plugins/image_gen/openai/__init__.py, tests/plugins/image_gen/test_openai_provider.py, tests/plugins/video_gen/test_deepinfra_provider.py, website/docs/user-guide/features/image-generation.md

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #65312 feat(image_gen): support base_url and key_env in OpenAI image config · superseded by another PR → #18796
  • #65323 feat(image_gen): support configurable endpoint, credential routing, and proxy bypass for OpenAI image generation · merged via another change → e113c1b, #115803, #65309, #97928, #13798, #60748, #64888, #65312, #64893, #60749
Closed issues · 1
  • Closed#65309[Feature]: Configure the OpenAI image endpoint and credential source in config.yaml
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
#115803
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
19 Sep 2026

For your agent

The same facts, typed.

cluster/65309.json
cluster/65309.md