CLI skill command cache and tab completion sync

NousResearch/hermes-agent · cluster 26441

Data as of

Nothing open on GitHub. Fix merged in #27382. 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 #27382. 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.

These issues and PRs concern keeping the CLI's skill command list and tab completion in sync when skills are reloaded or profiles change. Work spans reading commands from a live registry and invalidating stale caches in long-lived runtimes.

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.

  • #27382 Batch salvage group 5: 10 low-risk new-contributor PRs (codex-runtime-alias/qwen-1m/reload-skills/bedrock-lazy-deps/etc)

    merged to main

    files: acp_adapter/tools.py, agent/bedrock_adapter.py, agent/model_metadata.py, agent/shell_hooks.py, cli.py, gateway/platforms/telegram.py, hermes_cli/commands.py, hermes_cli/doctor.py, scripts/release.py, tests/acp/test_tools.py, tests/agent/test_model_metadata.py, tests/agent/test_shell_hooks.py, tests/gateway/test_restart_drain.py, tests/hermes_cli/test_commands.py, web/src/pages/ChatPage.tsx

3 PRs closed without merging

From the close comments: duplicate 2 · merged via another change 1

  • #26443 fix(cli): /reload-skills Tab completion update + _skill_commands sync · merged via another change → #27382
  • #26554 fix(cli): sync _skill_commands after /reload-skills so Tab completion updates · duplicate → #26443, #26441
  • #26557 fix(cli): sync _skill_commands after /reload-skills so Tab completion picks up new skills · duplicate → #26443, #26554
Closed issues · 1
  • Closed#26441/reload-skills does not update Tab completion for newly installed skills
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

Merged PRs
#27382
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
17 May 2026

For your agent

The same facts, typed.