Adom Bridge

@@ -209,11 +209,21 @@ Ask the user: **"What operating system is your desktop/laptop? (Windows, Mac, or 
 ### Step 4: Install & connect
 
-Run `adom-desktop setup_desktop` to get the `installer_url` and `server_config` fields. Then present **both options** to the user — the Claude Code prompt (fastest) and the manual steps (if they don't have Claude Code/Desktop):
+Run `adom-desktop setup_desktop` — it auto-detects this container's relay URL and returns a ready-to-run **`register_command`**, a fallback `server_config` JSON, and the `installer_url`. Prefer the zero-paste path:
 
 ---
 
-**Option A: Automatic setup via Claude Code (recommended)**
+**Option 0: Zero-paste via your Adom account (PREFERRED)**
+
+Run the **`register_command`** that `setup_desktop` returned (it's `adom-desktop register_container` with the name + URL filled in). That injects this connection into the **user's Adom cloud profile**. Then the user just:
+1. Installs Adom Desktop (from `installer_url`) and opens it,
+2. **Signs in with their Adom account** (Connections panel → "Sign in to Adom"),
+
+and the connection appears in their list and auto-connects — **no JSON paste at all**. This is the modern path and the one to try first. (`register_container` needs an Adom cloud container — it uses the mounted account token — and returns `ok:false` on a non-Adom box; if so, use Option A/B below.)
+
+---
+
+**Option A: Automatic setup via Claude Code (paste fallback)**
 
 If you have **Claude Code** or **Claude Desktop** on your laptop, paste this prompt:
 

⋯ 1 unchanged line ⋯

@@ -1,6 +1,6 @@ {
   "slug": "adom-desktop",
-  "version": "1.9.170",
+  "version": "1.9.171",
   "type": "app",
   "description": "Adom Desktop is a small operating system for AI on your Windows PC: it gives an AI real hands on your native desktop, including your signed-in browser, KiCad, Fusion 360, the shell, files, windows and screenshots. It provisions its own Node and Python so bridges run without touching your setup, and it talks straight to your machine. It ships with Hydrogen Desktop and installs standalone too, so if you drive your PC with Claude Desktop or another AI, this is what gives that AI hands.",
   "discovery_pitch": "Use when a cloud AI needs to reach a real Windows desktop: run shell commands, capture screenshots, drive native apps and browsers, transfer files, and control KiCad / Fusion 360 / third-party bridges.",

@@ -1,6 +1,6 @@ {   "slug": "adom-desktop",-  "version": "1.9.170",+  "version": "1.9.171",   "type": "app",   "description": "Adom Desktop is a small operating system for AI on your Windows PC: it gives an AI real hands on your native desktop, including your signed-in browser, KiCad, Fusion 360, the shell, files, windows and screenshots. It provisions its own Node and Python so bridges run without touching your setup, and it talks straight to your machine. It ships with Hydrogen Desktop and installs standalone too, so if you drive your PC with Claude Desktop or another AI, this is what gives that AI hands.",   "keywords": [

@@ -17,6 +17,16 @@ adom-desktop ping               # {echo:"pong", status:"connected"} == the lapto 
 If `adom-desktop` isn't found → **§4 install**. If `ping` doesn't say `connected`, the relay isn't serving — start it: `adom-desktop serve --supervise` (v1.9.168+ — detaches + self-heals so it survives your session; a plain `serve &` dies when the session is torn down and leaves every connected desktop in an HTTP 500 reconnect loop). Then re-`ping`.
 
+### Connecting a desktop for the FIRST time — run `setup_desktop`, don't hand-build JSON
+
+If no desktop is connected yet (`adom-desktop targets` shows none) and you need to set one up, **run `adom-desktop setup_desktop`** (aliases: `connect`, `setup`, `connect_info`). It auto-detects this container's public relay URL and hands you everything. **Do NOT assemble the connection JSON yourself** — guessing the URL/fields is the #1 setup failure (wiki issue #8).
+
+**PREFERRED — zero paste (the modern path):** `setup_desktop` returns a ready-to-run **`register_command`**. Run it — it's `adom-desktop register_container` with the name + URL filled in, and it writes this connection into the **user's Adom account** (their cloud profile). Then the user just **installs Adom Desktop and signs in with their Adom account**, and the connection appears in their list and auto-connects — no JSON paste at all. (`register_container` needs an Adom cloud container — it uses the mounted account token; it returns `ok:false` on a non-Adom box.)
+
+**FALLBACK — paste-JSON:** if `register_container` returns `ok:false` (not an Adom cloud container, or the user won't sign in), have the user paste the `server_config` JSON that `setup_desktop` returned into AD's Connections → "Paste server JSON to add" box.
+
+Either way, start the relay here so the desktop has something to dial: `adom-desktop serve --supervise`. Verify with `adom-desktop targets`.
+
 ## 2 — ⭐ DISCOVER THE VERB: `adom-desktop commands` (NOT `--help`)
 
 This is the step that's most often skipped, and skipping it is why calls get hand-rolled with `shell_execute` and fumble. **`adom-desktop --help` only lists `serve` / `install`** — every real capability is a *dynamic verb* forwarded to the laptop, and the authoritative, machine-readable catalog (200+ verbs, each with args + return shape + a `_hint`) is:

@@ -209,11 +209,21 @@ Ask the user: **"What operating system is your desktop/laptop? (Windows, Mac, or 
 ### Step 4: Install & connect
 
-Run `adom-desktop setup_desktop` to get the `installer_url` and `server_config` fields. Then present **both options** to the user — the Claude Code prompt (fastest) and the manual steps (if they don't have Claude Code/Desktop):
+Run `adom-desktop setup_desktop` — it auto-detects this container's relay URL and returns a ready-to-run **`register_command`**, a fallback `server_config` JSON, and the `installer_url`. Prefer the zero-paste path:
 
 ---
 
-**Option A: Automatic setup via Claude Code (recommended)**
+**Option 0: Zero-paste via your Adom account (PREFERRED)**
+
+Run the **`register_command`** that `setup_desktop` returned (it's `adom-desktop register_container` with the name + URL filled in). That injects this connection into the **user's Adom cloud profile**. Then the user just:
+1. Installs Adom Desktop (from `installer_url`) and opens it,
+2. **Signs in with their Adom account** (Connections panel → "Sign in to Adom"),
+
+and the connection appears in their list and auto-connects — **no JSON paste at all**. This is the modern path and the one to try first. (`register_container` needs an Adom cloud container — it uses the mounted account token — and returns `ok:false` on a non-Adom box; if so, use Option A/B below.)
+
+---
+
+**Option A: Automatic setup via Claude Code (paste fallback)**
 
 If you have **Claude Code** or **Claude Desktop** on your laptop, paste this prompt:
 

@@ -1,16 +1,16 @@ {
   "manifest_version": 1,
-  "version": "1.9.170",
-  "released_at": "2026-07-24T03:15:00Z",
+  "version": "1.9.171",
+  "released_at": "2026-07-24T04:05:00Z",
   "windows": {
-    "installer_url": "https://wiki.adom.inc/download/adom/adom-desktop/1.9.170/Adom.Desktop_1.9.170_windows_x64-setup.exe",
-    "installer_filename": "Adom.Desktop_1.9.170_windows_x64-setup.exe",
-    "installer_sha256": "61e4048362abae6771d0ec62ed338b78fcc1f1b9173c213e04f57f8acbfb0722",
-    "installer_size": 13500648
+    "installer_url": "https://wiki.adom.inc/download/adom/adom-desktop/1.9.171/Adom.Desktop_1.9.171_windows_x64-setup.exe",
+    "installer_filename": "Adom.Desktop_1.9.171_windows_x64-setup.exe",
+    "installer_sha256": "510b2e48d1952f974e93499ad5579d7b80eb080658e0307caf98b17ce2e102d3",
+    "installer_size": 13512088
   },
   "changelog_url": "https://wiki.adom.inc/adom/adom-desktop",
   "minimum_required": "1.3.30",
-  "note": "Fixes container shell ops: the Linux CLI now forwards the `reason` field on shell_execute, so shell_execute/run_script/wsl_exec work again against a 1.9.159+ desktop (issue #25). `adom-wiki pkg update` to get the fixed container CLI.",
+  "note": "Connection setup is one command now: `adom-desktop setup_desktop` (or `connect`) returns a ready-to-run register_container command that injects the connection into your Adom account, so it auto-appears when you sign in to Adom Desktop. No JSON paste on the common path.",
   "macos": {
     "installer_url": "https://wiki.adom.inc/download/adom/adom-desktop-macos/1.9.162/Adom.Desktop_1.9.162_macos_aarch64.dmg",
     "installer_filename": "Adom.Desktop_1.9.162_macos_aarch64.dmg",