Adom Hydrogen

@@ -1,67 +1,163 @@ # Hydrogen Desktop -**The full Adom Hydrogen workspace as a native Windows app — AI-driven electronics design, running locally.**+**The entire Adom Hydrogen workspace as a native Windows app — your editor, the AI agent, your repositories, and the full electronics‑design toolchain, running locally on your own machine.** -![Hydrogen Desktop — your workspace is ready](screenshots/hero.png)+![Hydrogen Desktop — your workspace is ready](screenshots/00_workspace-ready.png) -Hydrogen Desktop is the entire Adom Hydrogen experience — the editor, the AI agent, your repositories, molecules, and the electronics-design toolchain — packaged as one signed Windows application that runs on your own machine. Sign in with your Adom account and Hydrogen Desktop provisions a complete local workspace for you: a Linux dev environment, VS Code, Claude Code, the Gallia skills for schematic + PCB work, and a desktop bridge to your local hardware. No browser tab, no cloud container to wait on — it's your workspace, local and fast.+Hydrogen Desktop (HD) is the whole Adom Hydrogen experience packaged as one signed Windows application. Sign in with your Adom account and HD provisions a complete local workspace for you: a Linux dev environment (WSL2), VS Code, Claude Code, the Adom skills + CLIs for hardware design, and a live bridge to your desktop — all set up automatically, hands‑off, in a couple of minutes. -> **Windows only.** Hydrogen Desktop is a signed Windows desktop application (`.exe`). `adompkg install` on a Linux/WSL2 container only **stages** the installer — it does not run it. Copy the staged `.exe` to a Windows machine and run it there.+You write code and design boards locally; Adom is your identity and your toolchain. Nothing about your work has to live in the cloud. -## What you get+--- -After a one-time guided setup, Hydrogen Desktop gives you a ready-to-use, fully local workspace:+## What you get -- **VS Code** with the Adom workspace, dark mode, and a clean layout.-- **Claude Code** wired in and ready to pair — drive the whole environment in natural language.-- **Gallia skills** for hardware design — schematic capture, PCB layout, KiCad + Fusion automation, part search.-- **Desktop bridge** connecting the workspace to your local machine (KiCad, Fusion 360, Puppeteer/Chrome).+- **A full Linux dev workspace** — Ubuntu 24.04 (WSL2), VS Code (code‑server) with a clean dark layout, ready the moment setup finishes.+- **Claude Code, built in** — the AI agent is wired into the editor and the terminal, signed in with your Claude subscription.+- **The Adom toolchain** — `adom-cli`, parts search (Mouser/DigiKey/JLCPCB), KiCad/Fusion bridges, the wiki client, and 59 `hd-*` skills, all kept current automatically.+- **A bridge to your real desktop** — drive KiCad and Fusion 360, send files, capture screenshots, and control your browser, straight from the workspace.+- **Signed and self‑updating** — one verified publisher; the in‑workspace updater keeps your skills and tools fresh without you lifting a finger. -![Hydrogen Desktop's native menu — dev tools, container controls, zoom, fullscreen](screenshots/menu.png)+---  ## Install -This wiki package stages the signed Windows installer:+1. **Download** the latest `Hydrogen Desktop … x64‑setup.exe` from the releases on this page.+2. **Run it.** The installer is signed by *Adom Industries, Inc.* (same publisher as Adom Desktop), so Windows SmartScreen recognizes it. It installs per‑user — no admin prompt — and launches HD when it finishes.+3. **Sign in** with your Adom account. That's the only thing HD needs from you up front.++From there, HD takes over and sets the workspace up for you.++---++## First run: the automated setup++On first launch HD runs a **19‑step setup cascade**. It is fully automated and streams every step live, with exactly **one human moment** (signing in to Claude). It builds the Linux workspace, wires up the editor and the toolchain, proves every connection actually works, and ends by opening your first AI conversation.++Each step below shows what HD is doing and why it matters. The whole thing takes ~2–4 minutes on a typical machine (most of it the one‑time workspace download).++### Phase 1 — Build the workspace runtime++**1. Ensure workspace runtime**+Builds the WSL2 Ubuntu workspace (`Adom‑Workspace`): enables WSL2 if needed, downloads + SHA‑verifies the pre‑baked golden image, imports it, and starts code‑server. *Why:* this Linux environment is where everything else runs; the cascade won't advance until it's genuinely ready.+![Ensure workspace runtime](screenshots/01_ensure-workspace_done.png)++**2. Wait for code‑server**+Waits for code‑server (VS Code in the browser) to finish booting and serve HTTP. *Why:* the editor pane can't load until code‑server is actually answering.+![Wait for code-server](screenshots/02_wait-codeserver_done.png)++### Phase 2 — Wire up the editor + environment++**3. Activate editor extensions**+The `adom-vscode` extension is pre‑baked into the image, so nothing installs here — HD reloads the editor and verifies the `:8821` editor‑control API answers. *Why:* this proves the extension actually *activated*; every later editor action depends on it.+![Activate editor extensions](screenshots/03_install-adom-vscode_done.png)++**4. Set environment variables**+Writes `ADOM_CARBON_URL` / `ADOM_HYDROGEN_URL` / `VSCODE_PROXY_URI` into the workspace. *Why:* the Adom tools read these to know how to reach the platform.+![Set environment variables](screenshots/04_set-env-vars_done.png)++**5. Inject API key**+Writes your Adom session token into the workspace and validates it against the platform. *Why:* so `adom-cli` and the tools authenticate as you — and it fails fast here if the token doesn't work.+![Inject API key](screenshots/05_inject-api-key_done.png)++**6. Configure VS Code**+Applies every editor preference in one pass: dark theme, clean status bar, no welcome tab, trusted‑domain settings, and a decluttered activity bar. *Why:* a focused, consistent editor instead of the default clutter.+![Configure VS Code](screenshots/06_configure-vscode_done.png)++### Phase 3 — Connect the desktop bridge + relay -```-adompkg install adom/hydrogen-desktop-```+**7. Ensure Adom Desktop**+Verifies the Adom Desktop companion app is running on Windows. *Why:* it's the bridge that lets the workspace reach your real machine (KiCad, Fusion, files, browser).+![Ensure Adom Desktop](screenshots/07_ensure-adom-desktop_done.png) -That places `Hydrogen.Desktop_<version>_x64-setup.exe` in your `~/Downloads`. Copy it to a Windows machine and run it.+**8. Start relay server**+Starts the relay inside the workspace (ports 8765/8766). *Why:* it's the channel the workspace and your desktop talk over.+![Start relay server](screenshots/08_start-relay_done.png) -On Windows, the installer is a single guided flow — it's signed by **Adom Industries, Inc.**, so Windows SmartScreen recognizes the publisher.+**9. Test direct connect**+Proves the fast container→desktop command path works. *Why:* confirm the quick path before relying on it.+![Test direct connect](screenshots/09_test-direct-connect_done.png) -![The signed Adom installer on Windows](screenshots/install.png)+**10. Register relay for file transfers**+Registers the relay with Adom Desktop for file streaming. *Why:* so "send this file to my desktop" actually works.+![Register relay for file transfers](screenshots/10_test-relay_done.png) -## First run — guided setup+**11. Verify adom‑cli reaches Adom**+A hard gate: confirms the workspace reaches Adom through `adom-cli` on both the cloud (carbon) path and the hydrogen proxy, retrying a few times. *Why:* if the workspace can't reach the platform, nothing downstream will work — so HD stops here rather than limp forward.+![Verify adom-cli reaches Adom](screenshots/11_test-adom-cli_done.png) -The first time you launch Hydrogen Desktop it runs a one-time setup cascade that stands up your local workspace:+### Phase 4 — Claude -1. Sign in with your Adom account (it drives your native browser — one approval and you're in).-2. Authorize Claude Code the same way.-3. Hydrogen Desktop enables WSL2 if needed (one Windows restart), imports the Adom workspace image locally, and starts VS Code, Claude Code, and the desktop bridge.+**12. Install Claude Code CLI**+Installs the Claude Code CLI (`claude`) into the workspace via the official `claude.ai/install.sh`. *Why:* as of golden image **v15** the CLI is no longer baked in (its setup needs a live user session), so HD installs it at runtime — here you can watch it land `claude 2.1.185` live. The Claude Code VS Code extension stays baked; this adds the matching terminal CLI.+![Install Claude Code CLI](screenshots/12_install-claude-cli_done.png) -When the cascade finishes you'll see **"Your workspace is ready"** with green checks across the board. From then on, launches are fast — the workspace is already on your machine.+**13. Claude Authentication**+The one human moment. HD restores your saved Claude credentials if they're still valid; if not, it highlights and clicks the **Claude.ai Subscription** button and you approve in the browser. *Why:* the AI agent needs to be signed in — and HD runs this last, after all the hands‑off work, so the only thing you do is this single sign‑in.+![Claude Authentication](screenshots/13_claude-auth_done.png) -## Requirements+### Phase 5 — Prove the workspace is truly usable, then the payoff -- Windows 10/11 (x64).-- WSL2 (Hydrogen Desktop enables it for you on first run; that step needs one restart).-- An Adom account (sign in on first launch).+**14. Verify workspace live link**+A gate: ensures the editor's live link to HD (the browser session) is connected. *Why:* the Welcome page opens through this link — without it, it would silently fail.+![Verify workspace live link](screenshots/14_ensure-sse_done.png) -## Talk to the AI+**15. Verify workspace synced to proxy**+A gate: confirms the editor pushed its rendered layout into the workspace state. *Why:* until it has, panel lookups 404 — so HD proves the layout is really there.+![Verify workspace synced to proxy](screenshots/15_verify-workspace_done.png) -Once you're in, Claude Code can drive the whole workspace. Try:+**16. Welcome**+Starts your first AI conversation — opens Claude Code, makes sure it's authenticated, and sends the first prompt. *Why:* this is the payoff — the moment the workspace becomes useful.+![Welcome](screenshots/16_welcome_done.png) -- "Open my repositories and show me what changed recently."-- "Create a new molecule and start a schematic."-- "Run the KiCad bridge and route the power traces on this board."-- "Re-run the setup step that failed."+**17. Open Welcome page**+A final hard gate: opens the Welcome page in HD's right pane and confirms the tab actually appeared. *Why:* a missing Welcome page is treated as a failure, never a silent skip.+![Open Welcome page](screenshots/17_open-welcome_done.png) -## Source & build+**18. Explore your EDA tools**+Opens a second Claude conversation that quietly detects which electronics‑design tools you use (KiCad, Fusion 360, Altium, OrCAD/Cadence) and comes back with what it found and what it could show you. *Why:* by the time you look over, an AI has already mapped your stack. Fully opt‑in — it never opens apps or writes code until you say so.+![Explore your EDA tools](screenshots/18_eda-discovery_done.png) -Hydrogen Desktop is built privately and shipped publicly. The source, build pipeline, and signing process live on the private **`adom/hydrogen-desktop-dev`** page (Adom employees only).+**19. Bring up your InstaPCB quotes**+Opens a third conversation that finds your InstaPCB quotes and the quoting engine, and offers to wire up a live loop that re‑prices your board as your KiCad design changes. *Why:* it connects your design work to real, current pricing. Also fully opt‑in.+![Bring up your InstaPCB quotes](screenshots/19_instapcb-quote_done.png)++When the cascade finishes, you're looking at a fully configured editor with Claude Code ready and your Welcome page open — exactly the screenshot at the top of this page.++---++## What's new in v15++Hydrogen Desktop's golden workspace image is **v15**, and it's built a fundamentally cleaner way:++- **Built entirely from signed packages.** The image is assembled from signed `adompkg` packages on [wiki.adom.inc](https://wiki.adom.inc) — no clone‑and‑build steps, every artifact SHA‑verified at install.+- **Self‑updating workspace.** An in‑workspace updater (`adom-workspace-updater`) re‑pulls newer skills, CLIs, and extensions on its own (shortly after boot, then periodically). Your tools stay current without a re‑install.+- **Leaner + faster.** ~400 MB compressed (down from ~650 MB) — the C/C++ build toolchain and docs were dropped since everything ships as pre‑built binaries. Faster download, smaller footprint.+- **Runtime Claude CLI.** The `claude` CLI is installed on first run (step 12) rather than baked, so it's always a clean, current install.++---++## Updating++You don't have to do anything. The workspace updater keeps your skills, CLIs, and extensions current automatically. When an editor extension updates, HD shows a one‑click "reload to apply" banner.  --- -*Signed by Adom Industries, Inc. · Windows x64 · Built on the Adom Hydrogen platform.*+## Uninstalling++Uninstall Hydrogen Desktop like any Windows app — **Settings → Apps → Installed apps → Hydrogen Desktop → Uninstall**, or run the bundled uninstaller. The WSL2 `Adom‑Workspace` distro is separate; if you also want to reclaim its disk space, remove it with `wsl --unregister Adom-Workspace` (this only touches HD's workspace — your other WSL distros and Docker Desktop are untouched). Your repositories live on the Windows side and are never inside the distro, so they're unaffected.++---++## Troubleshooting++- **The window isn't visible after launch.** HD 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 HD opened, and it continues automatically.+- **"Ensure workspace 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` — HD re‑imports a fresh v15 image on the next launch.+- **Something feels out of date.** The workspace self‑updates, but you can force it from the workspace terminal: `ADOMPKG_ALLOW_SUDO=1 adompkg install adom/hd-windows-bootstrap`.++---++## Under the hood++HD runs the `Adom‑Workspace` WSL2 distro **locally** on your machine — your Adom login is identity only. The relay server lives inside the workspace; HD connects to it as a bridge client. Bridges to KiCad, Fusion 360, and your browser are launched on demand. It's the full Adom Desktop feature set merged into one signed executable.