Cairn
NousResearch/hermes-agent

Fix has_any_sessions() returning false incorrectly

Cluster 351. Data as of

Nothing open on GitHub. Fix merged in #370 on 4 Mar 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #370. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #370. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where has_any_sessions() always returns false for certain users causes repeated onboarding prompts. These items address fixes using database session counts and disk-based session detection.

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.

  • #370 fix(session): use database session count for has_any_sessions

    merged to main

    files: gateway/session.py, tests/gateway/test_session.py

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #352 fix(gateway): detect prior sessions from disk in has_any_sessions() · superseded by another PR → #370
Closed issues · 1
  • Closed#351`has_any_sessions()` always returns False for single-platform users, causing repeated onboarding
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.67: 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
#370
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
4 Mar 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.

For your agent

The same facts, typed.

cluster/351.json
cluster/351.md