## Back to the defaults (1.0.222)

Right-click the rail > **Reset to defaults (what every Adom user sees)**, click it again to
confirm, or `POST /dock/reset`. It drops the PERSONAL layer only: apps you added locally, pins,
the draft manifest URL override, the rail's width and collapsed state, the reveal flags and the
caches, then reloads the curated list from the wiki. The behaviour toggles in Settings > Dock Bar
(arm delay, alt-pin, collapse on launch...) are settings, not additions, and stay. The API answer
lists what was cleared and the curated app count:

```bash
curl -sX POST "$BASE/dock/reset"

---
name: hydrogen-dock-windows
description: >-
  Windows companion to hydrogen-dock: drive the dock from an AI thread through
  the control API (GET /dock/apps, POST /dock/launch, close, refresh, reset).
  Use when asked to launch or relaunch a dock app or reset the dock.
---

# hydrogen-dock-windows — Windows companion to hydrogen-dock

Read **hydrogen-dock** (platform-generic) first. The parts below exist only in the Windows Hydrogen;
the macOS app does not have them.

## Driving the dock from an AI thread (the ralph loop)

You do not click. ah's control API (see the hydrogen-api skill for the base URL and
`hd_api`) presses the dock for you and hands back what happened, so the loop is:
change the app in the container, launch it through the API, read the transcript, look
at the dashboard, repeat. Every response carries `_hints` saying what to do next.

| call | what it does |
|---|---|
| `GET /dock/apps` | every app: `id`, `wiki_repo`, `name`, `mode`, `running`, `launching`, `tab_open` (from the layout, the truth after a reload), `url`, `health`, `last_launch` summary |
| `POST /dock/launch {id, relaunch?, timeoutSec?}` | presses the button. `relaunch` defaults to true: close the tab, recreate it, run the steps again. Waits for the launch to finish (default 240 s) and returns `ok`, `url`, `reason`, `status`, `elapsed_ms`, `tab_open` and `console`, the same transcript the user sees in the loading screen: every status phase, every command and its container stdout/stderr, the failing step verbatim |
| `POST /dock/close {id}` | removes the app's webview tab and forgets its running state. Does not stop the app's container process; the next launch's serve retires it, or stop it with `/workspace/exec` |
| `POST /dock/refresh {full?}` | re-reads the curated apps.json now (with `full:true` also every display, manifest path and hero); call it after publishing a new apps.json or dockbar.json instead of waiting for the 6-hour poll |

`id` is the dock id (`kicad`, `nb`, `codex`), the wiki repo (`adom/nb-bridge`) or its slug.

```bash

## Back to the defaults (1.0.222)

Right-click the rail > **Reset to defaults (what every Adom user sees)**, click it again to
confirm, or `POST /dock/reset`. It drops the PERSONAL layer only: apps you added locally, pins,
the draft manifest URL override, the rail's width and collapsed state, the reveal flags and the
caches, then reloads the curated list from the wiki. The behaviour toggles in Settings > Dock Bar
(arm delay, alt-pin, collapse on launch...) are settings, not additions, and stay. The API answer
lists what was cleared and the curated app count:

```bash
curl -sX POST "$BASE/dock/reset"