Cairn

Bot Chat desktop session handling and peer run fixes

NousResearch/hermes-agent · cluster 115174

Data as of

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

The short answer

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

These issues and pull requests address bugs where peer runs or DMs encountering an open Bot Chat in Desktop were handled incorrectly, including wrong writer assignment, incorrect turn routing, and misleading timeout error messages.

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.

  • #116838 fix(bot-mode): a DM or peer run into a Bot Chat open in Desktop is answered by that chat, on every transport (#114959, #115174, #115316, salvage #114962 #115175 #115318)

    merged to main

    files: gateway/platforms/api_server.py, gateway/platforms/api_server_runs.py, tests/gateway/test_peer_dm_into_open_bot_chat.py, tools/bot_live_delivery.py, tools/bot_mode_dm.py, tui_gateway/methods_bot_relay.py

  • #116885 fix(peer): a timed-out peer DM says the turn was accepted and is still running, not that the peer is unreachable (#113099, salvage #113102)

    merged to main

    files: hermes_cli/subcommands/peer.py, tests/hermes_cli/test_peer_dm_reporting.py, website/docs/user-guide/bot-mode.md

  • #116926 fix(api-server): peer dm and peer run into a Bot Chat open in Desktop are answered by that chat, not a second writer (#114959, #115174, salvage #114962 #115175)

    merged to main

    files: gateway/platforms/api_server.py, gateway/platforms/api_server_runs.py, hermes_cli/subcommands/peer.py, tests/gateway/test_peer_dm_into_open_bot_chat.py, website/docs/user-guide/bot-mode.md

1 PR closed without merging

From the close comments: merged via another change 1

  • #115175 fix(api-server): a peer run into a Bot Chat open in Desktop is that chat's turn, and its receipt drives the run (#115174) · merged via another change → #116926, #116885, #115174
Closed issues · 1
  • Closed#115174[Bug]: `hermes peer run` into a Bot Chat that Desktop holds live runs as a second writer — the /v1/runs sibling of #114959
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.40: 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
#116838, #116885, #116926
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
20 Sep 2026

For your agent

The same facts, typed.

cluster/115174.json
cluster/115174.md