NousResearch/hermes-agent

Kanban Codex MCP server name mismatch fix

Cluster 111707. Data as of 2026-10-26 12:29 UTC

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

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

Read #112265 Pick up a Lab task

A bug where Kanban workers fail to initialize when using the Codex App Server due to a mismatch between 'hermes-mcp' and 'hermes-tools' MCP override names. The members cover the bug report and related fix attempts addressing this naming inconsistency.

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.

#112265 fix(codex): Kanban workers on the Codex App Server start (hermes-tools MCP override name) (#111707, salvage #107337)

merged to main

files: agent/codex_runtime.py, agent/transports/codex_app_server.py, agent/transports/codex_app_server_session.py, agent/transports/hermes_tools_mcp_server.py, evals/kanban_scope_probe.py, hermes_cli/codex_runtime_plugin_migration.py, hermes_cli/codex_runtime_switch.py, tests/agent/transports/test_codex_worker_mcp_overrides.py

1 PR closed without merging

From the close comments: merged via another change 1

#111711 fix(kanban): align Codex MCP server override · merged via another change → 204f345, #112265

Closed issues · 1

Closed#111707[Bug]: Kanban workers using Codex App Server fail to initialize due to hermes-mcp / hermes-tools name mismatch

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

Merged PRs: #112265
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 16 Sep 2026

For your agent

The same facts, typed.

cluster/111707.json
cluster/111707.md