app
Adom Hydrogen
Public Made by Adomby adom
The whole Adom experience as one signed native app: your editor, your AI agent, and the full electronics design toolchain, running locally on your own machine.
← Commit history
README: 3 setup images (WSL build, Claude auth, AI threads) each w/ a paragraph; drop the per-step wall + redundant intro shot; hero->v3
2 files changed
+13−85
README.md+12−84@@ -2,8 +2,6 @@ **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 (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. You write code and design boards locally; Adom is your identity and your toolchain. Nothing about your work has to live in the cloud.@@ -32,97 +30,27 @@ 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.---**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.---### 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.---**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.---**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.---**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.---### Phase 3 — Connect the desktop bridge + relay--**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).---**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.---**9. Test direct connect**-Proves the fast container→desktop command path works. *Why:* confirm the quick path before relying on it.---**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.---**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.---### Phase 4 — Claude+On first launch HD runs a fully automated **19‑step setup cascade**. It streams every step live and finishes with exactly **one human moment** — signing in to Claude. It builds the Linux workspace, wires up the editor and toolchain, proves every connection actually works, and ends by opening your first AI conversations. The whole thing takes ~2–4 minutes on a typical machine (most of it the one‑time workspace download). Three moments are worth calling out. -**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.-+### 1 · It builds your Linux workspace -**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.-+HD's first and biggest job is creating the environment everything else runs in. It provisions a dedicated WSL2 Ubuntu distro called **`Adom‑Workspace`** — enabling the WSL2 feature first if your PC doesn't have it yet (the one point where HD may need a reboot, after which it picks right back up on its own), then downloading and SHA‑verifying a pre‑baked ~400 MB "golden" image, importing it, and starting code‑server (VS Code in the browser) inside it. The cascade refuses to advance until that environment is genuinely up and answering. From there it wires the editor to the platform in a handful of quick steps — reloading to activate the pre‑baked `adom‑vscode` extension, writing the Adom platform URLs, injecting and validating your Adom session token so every tool authenticates as you, and applying a clean dark VS Code layout. -### Phase 5 — Prove the workspace is truly usable, then the payoff+ -**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.-+### 2 · It connects everything, then asks you to sign in to Claude — once -**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.-+Before bringing the AI online, HD proves the workspace can actually reach what it needs: it confirms the **Adom Desktop** companion app is running, starts the in‑workspace relay, and tests both the fast direct path and the file‑transfer path — with a hard gate that `adom‑cli` reaches Adom on both the cloud and the proxy routes (if it can't, HD stops here rather than limp forward). Then it installs the Claude Code CLI and reaches the **one and only step that needs you**: signing in to Claude. HD restores your saved Claude credentials if they're still valid; otherwise it highlights and clicks the **Claude.ai Subscription** button and you approve in the browser. HD deliberately saves this single human moment for last, after all the hands‑off work is already done. -**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.-+ -**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.-+### 3 · It opens your first AI conversations for you -**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.-+With everything wired up, HD doesn't drop you at an empty editor — it **starts your first AI conversations automatically**. It opens the Welcome thread (your first prompt already sent), then quietly spins up two more: one that detects which electronics‑design tools you use (KiCad, Fusion 360, Altium, OrCAD/Cadence) and reports back what it found, and another that locates your InstaPCB quotes and offers to wire up a live loop that re‑prices your board as your KiCad design changes. By the time you glance over, an AI has already mapped your stack and lined up the next steps. Every one of these is **fully opt‑in** — nothing opens an app or writes code until you say so. -**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.-+ -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.+When the cascade finishes you're looking at a fully configured editor with Claude Code ready and your Welcome page open — the workspace shown in the hero at the top of this page. --- @@ -133,7 +61,7 @@ Hydrogen Desktop's golden workspace image is **v15**, and it's built a fundament - **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.+- **Runtime Claude CLI.** The `claude` CLI is installed on first run rather than baked, so it's always a clean, current install. ---
page.json+1−1@@ -19,7 +19,7 @@ }, "hero": { "type": "image",- "path": "screenshots/hero-v2.png"+ "path": "screenshots/hero-v3.png" }, "metadata": { "platform": "windows",