NousResearch/hermes-agent

Stale file writer entries persist after task completion

Cluster 114446. Data as of 2026-10-24 13:18 UTC

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

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

Read #114862 Pick up a Lab task

A bug where finished tasks (cron runs or subagents) remain recorded as concurrent sibling writers in file state, because forget_task() does not clear last-writer entries. Multiple fix attempts address purging stale writers and adding TTL expiry.

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.

#114862 fix(file-state): a finished cron run or subagent is no longer reported as a concurrent sibling writer (#114446, salvage #114470)

merged to main

files: agent/client_lifecycle.py, contributors/emails/[redacted:email], tests/tools/test_file_state_registry.py, tools/file_state.py

2 PRs closed without merging

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

#114448 fix(tools): forget_task clears last-writer entries; stale writers expire · duplicate → #114470
#114470 fix(file_state): purge stale writer claims in forget_task and add writer TTL (#114446) · merged via another change → 783f854, #114862, #114446, #114470

Closed issues · 1

Closed#114446file_state: stale _last_writer entries report a finished predecessor as a concurrent sibling; forget_task() never clears them

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: #114862
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 18 Sep 2026

For your agent

The same facts, typed.

cluster/114446.json
cluster/114446.md