Skip to content

The agent that grows with you

docs(webapp): describe sign-out behind the sign-in gate and where launch links work

emozillaac6415096037
diff --git a/website/docs/developer-guide/gateway-local-sessions.md b/website/docs/developer-guide/gateway-local-sessions.md
index d3493a3227a..4d58a83bb17 100644
--- a/website/docs/developer-guide/gateway-local-sessions.md
+++ b/website/docs/developer-guide/gateway-local-sessions.md
@@ -51,7 +51,10 @@ The server issues `session:operator` only at these existing trusted boundaries:
session token is the browser-hosted Desktop's credential: the gateway keeps it in its home so
Webapp tabs survive a restart, hands it out only through a one-use link minted for a same-user
control-socket peer, and replaces it on `hermes webapp --sign-out` and whenever the Webapp's
- listener fails to start, since its port then belongs to someone else.
+ listener fails to start, since its port then belongs to someone else. Behind the sign-in gate a
+ Webapp login is bound to that token by the `hermes_webapp_signin` cookie (HMAC-SHA256 of
+ `webapp-sign-in` keyed with the token), so replacing it ends those logins too; sign-out closes
+ every socket the token or a bound login opened, Bot Desktop viewers included.
- The HTTP mutation gate, after a verified dashboard Session, native HTTP owner grant,
or permitted legacy session token has been accepted.
diff --git a/website/docs/reference/cli-commands.md b/website/docs/reference/cli-commands.md
index ff0f4afd7b0..f593ca8c120 100644
--- a/website/docs/reference/cli-commands.md
+++ b/website/docs/reference/cli-commands.md
@@ -1937,9 +1937,9 @@ use. See [Desktop App → Use the Desktop workspace from a browser](../user-guid
The link is valid for 60 seconds and works once; the browser exchanges it for the sign-in it keeps in
that tab. Only your own OS user can get a link: the gateway answers this command over its private
-control socket. On macOS, where a one-use link cannot be checked against your OS user, the command
-prints the gateway's private link instead and never passes it to a browser launcher. That link signs a
-browser in as you until you run `hermes webapp --sign-out`; keep it private.
+control socket. On macOS and the BSDs, where a one-use link cannot be checked against your OS user,
+the command prints the gateway's private link instead and never passes it to a browser launcher. That
+link signs a browser in as you until you run `hermes webapp --sign-out`; keep it private.
For a named profile served by the default gateway (`hermes -p work webapp`), the Webapp opens on that
profile.
@@ -1957,7 +1957,7 @@ is not built yet is the exception: this command builds it, and the running gatew
| `--force-build` | Rebuild the bundle even when its build receipt is current |
| `--build-only` | Build the bundle and stop |
| `--status` | Show whether the running gateway serves the Webapp, and at which address |
-| `--sign-out` | Sign out every tab a link signed in; their connections close and each needs a new link |
+| `--sign-out` | Sign out every browser: tabs a link signed in need a new link, and behind the sign-in gate every login must sign in again. Their connections close and the command reports how many. Waits for a gateway that is still starting; with none running, replaces the stored credential |
```bash
# Turn it on once, then open it
diff --git a/website/docs/user-guide/desktop.md b/website/docs/user-guide/desktop.md
index 27f55993e92..1e08cd996f9 100644
--- a/website/docs/user-guide/desktop.md
+++ b/website/docs/user-guide/desktop.md
@@ -53,9 +53,11 @@ serves the CLI, the native Desktop and messaging, so every surface sees one conv
keeps in that tab, so reloading keeps you signed in, and so does a gateway restart. A fresh tab or a
bare URL shows instructions instead of access: run `hermes webapp` again for a new link. **New
Window**, profile windows and session pop-outs hand the sign-in over with their own one-use link. On
-macOS the command prints the gateway's private link instead, for you to open; it signs a browser in as
-you until you sign out, so keep it private. `hermes webapp --sign-out` signs out every tab at once: their
-open connections close and each shows the sign-in instructions.
+macOS and the BSDs the command prints the gateway's private link instead, for you to open; it signs a
+browser in as you until you sign out, so keep it private. `hermes webapp --sign-out` signs out every
+tab at once: their open connections close, Bot Desktop viewers included, and each shows the sign-in
+instructions. Behind the sign-in gate (below) it also signs out every browser that signed in with a
+dashboard account; each must sign in again.
For a named profile, `hermes -p work webapp` opens the Webapp on `work`. Profiles the default gateway
serves share its Webapp; a standalone profile's own gateway serves its own when its config turns it on.