Adom Hydrogen

@@ -128,6 +128,7 @@ Hover a card and dwell, and it zooms to a full billboard so you can actually rea Click the teal Adom logo in the top-left corner for the app-level menu:  - **Settings**, **Ports...**, and the **API Explorer** for browsing and testing every control-API endpoint (the same API external AIs use to drive Hydrogen).+- **Doctor...** and **Run Wake Check**: a full health scan of the whole stack with a one-click fix, and a manual run of the same repair Hydrogen performs automatically when your laptop wakes from sleep. - **Desktop**: jump to Adom Bridge, zoom, fullscreen, the console, and Developer Tools. Hydrogen is a developer tool; DevTools are for everyone. - **Container**: restart or stop the Linux container without leaving the app. - **Admin**: re-open the Setup Steps, run a Virgin Reset (wipe the container and re-run the full first-run setup), and manage the Browser Picker.@@ -146,6 +147,8 @@ Type size works on two independent levels, on purpose: the **editor code font si  A live map of every port Hydrogen binds, across both layers: the Windows frontend (Control API, Container Proxy, WebView2 CDP, discovery, the direct API, the Bridge liveness beacon) and the Linux container backend (code-server, the relay, shotlog, bridges). Read live on every refresh; mirrored networking status up top explains how the frontend reaches the backend. +Hydrogen prefers well-known ports (code-server 7380, control API 47084 and neighbors) but never fights over them: if a port is taken, it binds a free one the OS hands out and records the result, so nothing breaks on a busy machine. Everything that needs to find Hydrogen reads the live assignments rather than assuming defaults, and on every launch Hydrogen also publishes its current address to your Adom account (a small entry in your cloud settings). That last part means an AI agent, even one running in a cloud container or on another of your machines, can find your running Hydrogen without any port guessing.+  ### API Explorer @@ -153,6 +156,18 @@ Browse and try every endpoint of Hydrogen's control API, the same API external A  <img src="screenshots/api-explorer.png" alt="The API Explorer: every control-API endpoint, browsable and testable" width="640"> +### Doctor++When something feels broken and you don't know what, open the Doctor. It runs about seventeen real end-to-end checks across the whole stack: the Linux container, your Adom and Claude sign-ins, the editor backend, the extensions, the live event link, the ports, and the Adom Bridge connection. Each row explains itself in plain English when you hover it, so a red mark tells you what is actually wrong, not just that something is.++Two buttons do the repairing. **Fix problems** runs the safe repair (the same one the wake recovery uses) and then re-runs every check so you can see the before and after. **Restart workspace** is the bigger hammer, and Hydrogen only offers it when the safe fix wasn't enough; it asks first, because it reloads your editor for about thirty seconds. Your AI can run the Doctor too (it's on the control API), so "hey, something's broken" in chat is a legitimate way to start.++### Run Wake Check++Laptops sleep, and the Linux world inside WSL2 sometimes wakes up groggy. Hydrogen detects the wake and repairs the connection automatically: it confirms the editor backend is genuinely serving again, restores credentials the sleep wiped, and un-sticks the editor pane if it froze, all before you notice. A small indicator in the header (optional, in Settings) shows the repair happening with a live play-by-play tooltip.++**Run Wake Check** in the Adom menu triggers that same repair on demand and keeps the play-by-play pinned open so you can watch it work. And if the workspace ever dies without a sleep event, Hydrogen notices that too: the editor shows a banner with a **Reconnect** button instead of leaving you staring at a frozen pane.+ ### Console  The Console is Hydrogen's own flight recorder, live: a tail of the app log (heartbeats, the Bridge health supervisor, workspace state changes, window lifecycle) with Pause and Clear view. Fittingly, it opens inside a Hydrogen Browser Window, the app using its own surfaces to watch itself.@@ -259,6 +274,8 @@ mechanism, its cadence, and the thundering-herd design rules (why a large fleet accidentally DoS this wiki) are documented in the [Auto-Updates sub-readme](https://wiki.adom.inc/adom/hydrogen/files/auto-updates/README.md). +You can also just ask your AI. The updater is on the control API (check, status, and install), so "is there a Hydrogen update?" in chat gets you both version numbers, and "update it" applies the staged version and relaunches; the container keeps running, so your session reconnects in seconds.+ ---  ## Uninstalling@@ -269,6 +286,8 @@ Uninstall Hydrogen like any Windows app — **Settings → Apps → Installed ap  ## Troubleshooting +- **Something broke and you don't know what.** Adom menu → **Doctor...** → Fix problems. It diagnoses the whole stack with plain-English results and repairs what it safely can.+- **Frozen after your laptop slept.** Hydrogen normally heals this on its own; if it didn't, Adom menu → **Run Wake Check** (or the Reconnect button on the editor banner). - **The window isn't visible after launch.** Hydrogen may have started minimized — check the taskbar. It runs in the background during setup. - **Setup paused at "Claude Authentication."** That's the one human step — approve the sign‑in in the browser window Hydrogen opened, and it continues automatically. - **"Ensure container runtime" won't complete.** Make sure WSL2 is healthy (`wsl --version`, `wsl -l -v`). A stale or corrupt `Adom‑Workspace` distro can be reset with `wsl --unregister Adom-Workspace` — Hydrogen re‑imports a fresh v15 image on the next launch.