docs: split remote control docs

README.md

@@ -10,20 +10,15 @@ you. Remote control from your phone when you're in motion.
 
 ## Why agentd?
 
-Modern development often means asking several agents to investigate, edit, test,
-review, or monitor the same project. `agentd` turns that from a pile of orphaned
-CLI windows into a managed fleet — fast to read, tactile to drive, and built for
-dense, high-signal engineering work:
-
 - **One cockpit for every agent** — attach to Claude Code, Codex, Antigravity,
   Zarvis, or a shell process from one focused workspace that rewards attention.
 - **Parallel work without losing control** — spawn helper sessions, pin important
   work, interrupt stuck runs, inspect diffs, and send follow-up input mid-turn.
 - **Agent-to-agent orchestration** — MCP tools let an agent list sessions, read
   output, spawn helpers, send input, inspect diffs, and drive Chrome.
-- **Remote control when you step away** — `/remote-control` opens a
-  browser-accessible web client with a QR code. Connect from your phone, no
-  service signup, no setup required.
+- **[Remote control](docs/remote-control.md) when you step away** — `/remote-control`
+  opens a browser-accessible web client with a QR code. Connect from your phone,
+  no service signup, no setup required.
 - **Extensible harness protocol** — adapters are separate processes speaking
   JSON-RPC over stdio, so new tools can plug in without changing the daemon.
 
@@ -111,8 +106,10 @@ For an optimized build, use `cargo build --workspace --release` and replace
   approvals, automode, and hooks.
 - [Unified tool layer](docs/unified-tool-layer.md) — MCP servers and shared tools for
   fleet control, browser automation, and agent coordination.
-- [Configuration](docs/configuration.md) — XDG paths, `AGENTD_*` overrides,
-  remote-control setup, and TUI theme customization.
+- [Configuration](docs/configuration.md) — XDG paths, `AGENTD_*` overrides, and
+  TUI theme customization.
+- [Remote control](docs/remote-control.md) — phone/browser access, QR setup,
+  credentials, and local debug mode.
 - [Releasing](docs/RELEASING.md) — how the prebuilt binaries are built and
   published, and how to cut a versioned release.
 - [Contributor workflow](AGENTS.md) — PR workflow, build expectations, and TUI

docs/configuration.md

@@ -13,26 +13,6 @@
 
 `agentd paths` prints the resolved layout.
 
-## Remote control
-
-`/remote-control` exposes the running daemon through a browser-accessible web
-client so you can check and steer the same fleet from another device. The TUI
-shows a modal with a URL, QR code, username, and password; the local modeline
-shows a `remote` badge while remote clients are attached.
-
-| Command / setting | Purpose |
-|---|---|
-| `/remote-control` | Start the local WebSocket server and public tunnel, then show URL + QR code. |
-| `/remote-control <password>` | Start remote control with a user-chosen password. |
-| `/remote-control stop` | Stop the remote listener/tunnel and rotate credentials for the next start. |
-| `/remote-control debug` | Start a local-only URL without a public tunnel; useful for troubleshooting. |
-| `AGENTD_REMOTE_WS_PORT=<port>` | Start the remote WebSocket listener on daemon boot for scripted/headless use. |
-
-Remote-control sessions use HTTP basic auth. The username is `remote`; the
-password is generated per session unless supplied explicitly. Public tunnel
-state is persisted under the runtime directory so a daemon restart can preserve
-the active remote URL when possible.
-
 ## TUI Theme
 
 The TUI uses a built-in Matrix theme by default. Override any color slot in

docs/remote-control.md

@@ -0,0 +1,19 @@
+# Remote control
+
+`/remote-control` exposes the running daemon through a browser-accessible web
+client so you can check and steer the same fleet from another device. The TUI
+shows a modal with a URL, QR code, username, and password; the local modeline
+shows a `remote` badge while remote clients are attached.
+
+| Command / setting | Purpose |
+|---|---|
+| `/remote-control` | Start the local WebSocket server and public tunnel, then show URL + QR code. |
+| `/remote-control <password>` | Start remote control with a user-chosen password. |
+| `/remote-control stop` | Stop the remote listener/tunnel and rotate credentials for the next start. |
+| `/remote-control debug` | Start a local-only URL without a public tunnel; useful for troubleshooting. |
+| `AGENTD_REMOTE_WS_PORT=<port>` | Start the remote WebSocket listener on daemon boot for scripted/headless use. |
+
+Remote-control sessions use HTTP basic auth. The username is `remote`; the
+password is generated per session unless supplied explicitly. Public tunnel
+state is persisted under the runtime directory so a daemon restart can preserve
+the active remote URL when possible.