docs(desktop): remote backends update separately + profile-skew troubleshooting - #40024
Closed
OutThisLife wants to merge 1 commit into
Closed
docs(desktop): remote backends update separately + profile-skew troubleshooting#40024OutThisLife wants to merge 1 commit into
OutThisLife wants to merge 1 commit into
Conversation
…symptom
When the desktop connects to a remote backend, the two are separate installs —
the desktop's one-click update only updates the local app, not the remote
backend. A newer desktop on an older backend silently misbehaves (new chats /
resumes routing to the wrong profile, since per-session profile routing is a
backend feature).
- Add a "Remote backends update separately" caution under Updating, with the
exact `hermes update` + dashboard-restart steps for the remote machine.
- Add a remote-Troubleshooting entry for the visible symptom ("new chats land in
the wrong profile / 'session not found' after switching profiles") pointing at
the backend-update fix and the "Backend out of date" skew warning.
OutThisLife
enabled auto-merge (squash)
June 5, 2026 18:32
daimon-nous
Bot
added
type/docs
6 tasks
5 tasks
auto-merge was automatically disabled
June 10, 2026 15:25
Pull request was closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the gotcha behind a real support case: a desktop updated to newer code while its remote backend stayed old, causing new chats / resumes to silently route to the wrong profile (per-session profile routing is a backend feature).
Two additions to
user-guide/desktop.md:"Remote backends update separately" caution under Updating — the one-click update only updates the local app; the remote backend is a separate install and must be updated on its own machine (
hermes update+ restart the dashboard). Calls out that desktop>backend skew can misroute sessions and that the app shows a "Backend out of date" warning.Remote Troubleshooting entry for the visible symptom — "new chats land in the wrong profile / 'session not found' after switching profiles" — pointing at the backend update and the skew warning.
Pairs with #40017 (the contract bump that makes the skew warning actually fire) and #40018 (feature request to auto-update the remote backend). Docs-only.