NousResearch/hermes-agent

Curator read-before-write guard fails across worker threads

Cluster 94324. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #94511 on 25 Aug 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 #94511. 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 #94511, then check it covers your case.

Read #94511 Pick up a Lab task

A bug where ContextVar-based skill_view marks are lost when crossing tool-call worker threads, causing the curator's read-before-write guard to always refuse patches or edits to existing skills. The members cover the bug report and several fix attempts addressing this thread-context propagation issue.

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.

#94511 fix(skills): background-review curator patches no longer refused after skill_view (#75618, salvage #73975)

merged to main

files: tests/tools/test_skill_manager_tool.py, tools/skill_manager_tool.py

2 PRs closed without merging

From the close comments: done elsewhere 2

#94326 fix(curator): let read-before-write guard pass across review tool worker threads (#94324) · done elsewhere → 335c60e, #94511, #73975, #94324
#94330 fix(skills): keep curator read marks across tool-call worker threads · done elsewhere → 335c60e, #94511, #73975

Closed issues · 1

Closed#94324[Bug] Background curator read-before-write guard can never pass: skill_view marks (ContextVar) are lost across tool-call worker threads, so every patch/edit of an existing skill is refused

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: #94511
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 25 Aug 2026

For your agent

The same facts, typed.

cluster/94324.json
cluster/94324.md