NousResearch/hermes-agent

Fix key_cmd token resolution in capability probes

Cluster 104460. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #104902 on 7 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #104902 Pick up a Lab task

These members address a bug where Ollama capability probes incorrectly sent the CommandTokenSource object representation instead of the actual minted credential when using key_cmd providers. Multiple fix attempts or approaches are represented for resolving token evaluation before the probe runs.

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.

#104902 fix: capability probes use minted credentials rather than callable text

merged to main

files: agent/command_token_source.py, agent/image_routing.py, agent/model_metadata.py, hermes_cli/models_local.py, tests/agent/test_capability_probe_credentials.py, website/docs/integrations/providers.md

2 PRs closed without merging

From the close comments: done elsewhere 2

#104477 fix(agent): mint the key_cmd token for capability probes, not the source repr · done elsewhere → 7d44fe9, bbbccd3, #104460, #104902, #87641
#104880 fix(cli): resolve key_cmd token before the Ollama capability probe · done elsewhere → #104460

Closed issues · 1

Closed#104460Ollama capability probe sends the CommandTokenSource object repr as the bearer for key_cmd providers

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

Merged PRs: #104902
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 7 Sep 2026

For your agent

The same facts, typed.

cluster/104460.json
cluster/104460.md