From 5ee6cfd1a940a8950af5df282cc2e9646d730d68 Mon Sep 17 00:00:00 2001 From: l0ng-ai <24760907+l0ng-ai@users.noreply.github.com> Date: Sat, 15 Aug 2026 01:19:38 +0800 Subject: [PATCH] docs(remote): document the machine badge, the forward switch, and the New Tab host menu --- docs/remote/port-forwarding.mdx | 22 ++++++++++++++++++++++ docs/remote/ssh.mdx | 9 ++++++++- docs/remote/workspaces.mdx | 20 ++++++++++++++++++++ 3 files changed, 50 insertions(+), 1 deletion(-) diff --git a/docs/remote/port-forwarding.mdx b/docs/remote/port-forwarding.mdx index 99e1b1aa..2446dfad 100644 --- a/docs/remote/port-forwarding.mdx +++ b/docs/remote/port-forwarding.mdx @@ -23,6 +23,28 @@ half-configured. Each rule takes an optional description — *"what it's for"* — because six months later `8080 → 3000` explains nothing. +## Switching a rule off + +The switch at the start of a rule decides whether the connection opens it. A +rule that is off is kept exactly as you wrote it and simply not offered to the +far side — which is what a forward for a service that is only up part of the +day needs, instead of deleting the rule and typing it in again twice a day. + +The section header counts both: *"2 rules, opened with the connection · 1 +switched off"*. + +A live forward has the same switch. In the **Forwards** panel, ⏸ takes the +listener down and keeps the row — faded, with ▶ beside it. Nothing is retyped +when it comes back. If the port has been taken in the meantime, the rule stays +off and says why rather than disappearing. + + + A live forward switched off this way comes back on when you switch it on, not + when you reconnect — the far side has no such thing as a paused listener, so + the rule is being kept by tty7 for this session. For something you want off + across sessions, switch the rule off in the profile. + + ## Adding one mid-session *SSH: Port Forwarding* in the command palette opens the **Forwards** panel for diff --git a/docs/remote/ssh.mdx b/docs/remote/ssh.mdx index af5d7fe8..9a25ed24 100644 --- a/docs/remote/ssh.mdx +++ b/docs/remote/ssh.mdx @@ -15,9 +15,16 @@ instead of a password echoing into your shell. Connecting over SSH in tty7 -## Four ways to connect +## Ways to connect + + The **+** button's menu lists your saved hosts under the shells, most + recently and often used first, each with the address behind its name. + Picking one opens the connection in a new tab. *Add Connection…* under them + opens the address box for a host you have not saved. + + Open the palette (⌘ P) and type an address. IPv6 works with brackets. diff --git a/docs/remote/workspaces.mdx b/docs/remote/workspaces.mdx index bd70c5eb..39ef8b33 100644 --- a/docs/remote/workspaces.mdx +++ b/docs/remote/workspaces.mdx @@ -46,6 +46,26 @@ Nothing is synced or copied. The repository stays where it is. +## Knowing which machine you are on + +A window on another machine says so, and keeps saying so. Under the workspace +name in the tab rail is a dot and the machine's name — green while the link is +up, amber while it is being made or remade, red once it has given up, with a +word beside it whenever the state is not the one you would assume: + +``` +[F] fable-marten ⌃⌄ + ● devbox · reconnecting +``` + +The tab rows below it stay quiet, because the badge above them already answered +the question. A row only names its own machine when that would *contradict* the +badge — an SSH pane opened inside a local workspace, or a `wsl` shell beside +Windows ones. + +An empty remote workspace has no rail to carry the badge, so the home screen +names the machine a new tab would open a shell on. + ## What gets installed | | |