Cairn
NousResearch/hermes-agent

sessions DB migration timing and schema fix

Cluster 80037 · dashboard. Data as of

Nothing open on GitHub. Fix merged in #86671 on 15 Aug 2026. Check it covers your case.

The short answer

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

These items address a missing 'last_read_at' column in the sessions schema that caused API failures, focusing on ensuring the database migration runs eagerly at startup rather than being deferred or silently skipped.

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.

  • #80797 fix(desktop): derive the stale-schema read probe from SCHEMA_SQL

    merged to main

    files: hermes_cli/web_routers/profiles.py, hermes_cli/web_server.py, hermes_state_schema.py, tests/hermes_cli/test_web_server.py, tests/test_schema_read_probe.py

  • #86671 fix(sessions): eager state.db schema migration at backend startup; stop swallowing locked ALTERs

    merged to main

    files: hermes_cli/web_server.py, hermes_state_schema.py, tests/hermes_cli/test_web_server.py, tests/test_hermes_state.py

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #80047 fix(sessions): heal missing last_read_at on read-only GET /api/sessions opens · superseded by another PR → #80797
Closed issues · 1
  • Closed#80037Session list API fails with "no such column: s.last_read_at" after update until first new session triggers migration
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

Subsystem
dashboard
Merged PRs
#80797, #86671
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
15 Aug 2026

For your agent

The same facts, typed.

cluster/80037.json
cluster/80037.md