Cairn

Session title deduplication and collision handling fixes

NousResearch/hermes-agent · cluster 50537 · agent

Data as of

Nothing open on GitHub. Fix merged in #66058. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #66058. 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.

Multiple fixes addressing duplicate auto-generated session titles, including handling of ValueError exceptions, atomic writes, race conditions, and collision deduplication for both regular and cron sessions.

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.

  • #66058 fix(title): atomic auto-title writes + collision dedup for sessions and cron (salvage #51483 + #50575)

    merged to main

    files: agent/title_generator.py, cron/scheduler.py, hermes_state.py, scripts/release.py, tests/agent/test_title_generator.py, tests/cron/test_scheduler.py, tests/test_hermes_state.py

4 PRs closed without merging

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

  • #26389 fix(agent): auto-deduplicate session titles on collision · other → #26471, #66058, #50575
  • #50538 fix(cron): improve cron session title reliability — nonblank titles, pre-close race fix, duplicate suffix hardening · done elsewhere → #50535, #50536, #50537, #66058, #50575
  • #50544 fix(title): handle duplicate auto-generated session titles gracefully · duplicate → #26389, #50537, #26471, #50538
  • #50575 fix(cron): robust session title generation · merged via another change → 9bf5822, #66058, #51483
Closed issues · 1
  • Closed#50537fix(title): duplicate auto-generated session titles cause unhandled ValueError
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.33: 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
agent
Merged PRs
#66058
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
17 Jul 2026

For your agent

The same facts, typed.

cluster/50537.json
cluster/50537.md