Cairn
NousResearch/hermes-agent

Replaying recent user images on turns rebuilt from session DB

Cluster 136216 · agent. Data as of

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

These members appear to address one theme: images sent through the API server not being available for follow-up questions, with changes that replay recent user images when turns are rebuilt from the session database. One member references supersession of another item, but the titles alone don't indicate the outcome.

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.

  • #139873 fix(agent): follow-up turns rebuilt from the session DB see the user's image again (#136216, supersedes #136217)

    merged to main

    files: agent/image_replay.py, agent/session_persistence.py, agent/turn_context.py, cli-config.yaml.example, gateway/session_ingress_media.py, hermes_cli/config_defaults.py, tests/agent/test_image_replay.py, website/docs/user-guide/configuration.md, website/docs/user-guide/features/vision.md

1 PR closed without merging

From the close comments: done elsewhere 1

  • #136217 feat(agent): replay recent user images on turns rebuilt from the session DB · done elsewhere → 28dd115, f86276d, 3e9c158, 424d0a0, e374e53, 055e7cc, #133281, #342057, #111827, #46115
Closed issues · 1
  • Closed#136216Images sent through the API server are lost for follow-up questions (replay recent images on rebuilt turns)
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

Subsystem
agent
Merged PRs
#139873
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
16 Oct 2026

For your agent

The same facts, typed.

cluster/136216.json
cluster/136216.md