NousResearch/hermes-agent

Queued send attachments targeting wrong chat session

Cluster 116285. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #116932 on 20 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #116932 Pick up a Lab task

A bug where queued sends with attachments recover and submit against the currently visible chat rather than their originating session, causing images and text to land in the wrong chat. The members cover the bug report and related fix attempts.

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.

#116932 fix(desktop): a queued send with attachments stages, recovers and submits to its own session, not the chat on screen (#116285, salvage #116287)

merged to main

files: apps/desktop/src/app/contrib/session-rpc-dispatcher.test.ts, apps/desktop/src/app/session/hooks/use-prompt-actions/index.test.tsx, apps/desktop/src/app/session/hooks/use-prompt-actions/index.ts, apps/desktop/src/app/session/hooks/use-prompt-actions/submit.ts, contributors/emails/[redacted:email]

1 PR closed without merging

From the close comments: merged via another change 1

#116287 fix(desktop): a queued send's attachments stage on, recover and submit to ITS session, not the chat on screen (#116285) · merged via another change → 3a6e963, #116932, #116285, #116287

Closed issues · 1

Closed#116285[Bug]: Desktop — a queued send with attachments recovers against the chat on screen, so its image and text land in the newly selected chat and rebind the origin chat to it (attachments residual of #46194 / #72165)

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: #116932
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 20 Sep 2026

For your agent

The same facts, typed.

cluster/116285.json
cluster/116285.md