Cairn

Bug fix: preserve skill command cache on scan failure

NousResearch/hermes-agent · cluster 18656 · skills

Data as of

4 open items. Fix attempted, not merged.

The short answer

1open issue
3open PRs
8items grouped
Known?
Yes. 8 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 3 PRs.

A bug was identified where scan_skill_commands() unconditionally clears the _skill_commands cache before the try block, silently losing all skills if the scan fails. These issues and PRs address preserving the existing cache when a scan error occurs.

Open issues1

  • Issue#18659[Bug]: scan_skill_commands unconditionally clears _skill_commands before try block, silently loses all skills on scan failure

Open PRs3

  • PR#18668fix(skills): preserve command cache on scan setup failure
  • PR#18720fix: preserve skill command cache on scan failure in scan_skill_commands()
  • PR#74511fix(skills): preserve _skill_commands cache when scan fails (#18659)

3 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1 · other 1

  • #18669 fix(agent): preserve skill commands on scan failure + log diagnostic warning · done elsewhere → #18669, #18659, #2868, #22514
  • #18717 fix(agent): preserve _skill_commands cache on scan failure; cap rglob fallback (#18659, #18675) · other → #18668, #18677, #18659, #18675
  • #22514 fix(skill_commands): preserve cache when scan fails · superseded by another PR → #18668
Closed issues · 1
  • Closed#18656scan_skill_commands: unconditionally clears _skill_commands before try block
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.23: 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
skills
Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/18656.json
cluster/18656.md