NousResearch/hermes-agent

Custom opencode provider routing and tool-name fixes

Cluster 85589 · agent. Data as of 2026-10-29 11:48 UTC

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

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #91268. 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.

Next step: read #91268, then check it covers your case.

Read #91268 Pick up a Lab task

These members address routing failures and reserved tool-name collisions for custom opencode-go-* providers, along with related fixes for model routing and grok model support.

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.

#91268 fix(providers): custom opencode-* providers route per model and dodge reserved tool names (#85589, salvage #85619)

merged to main

files: agent/agent_runtime_helpers.py, agent/transports/codex.py, cli.py, contributors/emails/[email protected], hermes_cli/model_normalize.py, hermes_cli/model_switch.py, hermes_cli/models.py, hermes_cli/runtime_provider.py, tests/agent/transports/test_codex_transport.py, tests/hermes_cli/test_custom_opencode_family_runtime.py, tests/hermes_cli/test_model_validation.py

1 PR closed without merging

From the close comments: merged via another change 1

#85619 fix(providers): support custom opencode-go-* provider routing and grok models · merged via another change → #91268, #85589

Closed issues · 1

Closed#85589Custom `opencode-go-*` provider doesn't route through opencode family (503) + reserved tool-name collision (400)

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.67: 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: #91268
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 21 Aug 2026

For your agent

The same facts, typed.

cluster/85589.json
cluster/85589.md