docs: explain gateway session groups and saved Cloud switching
This commit is contained in:
@@ -81,6 +81,27 @@ cron stay scoped to that gateway; the app-managed window backend is still chosen
|
||||
by the connection-mode controls above. **Primary** is the registry fallback and
|
||||
does not switch the current workspace.
|
||||
|
||||
## Organizing session groups
|
||||
|
||||
In the Sessions sidebar's view menu, choose **Gateway & profile** while viewing
|
||||
all profiles. Each gateway/profile pair gets its own collapsible section, so two
|
||||
gateways with a `default` profile no longer share a section. Section labels start
|
||||
as the gateway name followed by the profile name.
|
||||
|
||||
Use a section's menu to **Rename group**, **Reset name**, **Move up**, or
|
||||
**Move down**. Renaming changes only the sidebar label, not the gateway or profile.
|
||||
Drag the section's leading icon to reorder it, or focus that handle and use
|
||||
Space, arrow keys, then Space to place it. Names, order, and collapsed sections
|
||||
are remembered on this desktop. The section's new-session action targets that
|
||||
section's gateway and profile.
|
||||
|
||||
The Hermes Cloud panel also lists **Saved Cloud gateways** when portal discovery
|
||||
is signed out. **Use gateway** selects an existing saved connection without
|
||||
changing the default gateway; **Active in this window** identifies the current
|
||||
one. Adding a new instance uses its friendly Cloud name, while existing custom
|
||||
connection names are preserved. Saved connections still need valid gateway
|
||||
authentication; manage sign-in from the registered connection controls.
|
||||
|
||||
## Adding a connection, step by step
|
||||
|
||||
1. Open **Settings → Gateways** and scroll to the connections registry (or
|
||||
|
||||
Reference in New Issue
Block a user