Connecting with hydrogen container

by adom

Adom Bridge unleashes your AI onto your full PC: full power, full safety. The AI breaks out of the container it runs in and onto your real machine, managing and running your entire laptop as you: launch apps, move files, drive any window, control KiCad, Fusion 360 or your real signed-in browser. Works with any AI, cloud or local (Claude Desktop, Claude Code, Codex), no Hydrogen required. Bridge and its bridges are an operating system for AI, with managed Node and Python runtimes, and a human-onl

Overview Files Skills Discover Packages Releases Dependencies Issues40 Breadcrumbs Pull Requests Activity

Closed bug report

kaleymer · 1mo ago ·closed by John Lauer

Hydrogen (claude) always struggles to know what JSON to create for the desktop server. I often have to ask it multiple times to search around and/or give it example json from another connection.

2 Replies

John Lauer · 26d ago

Thanks for the report. The friction is real: the connection JSON shape was underdocumented, so Claude guesses. What exists today:

The canonical JSON (paste into the AD window's "Paste server JSON to add" box, or drop into ~/.adom/config.json under servers):

{"name": "galliaApril", "url": "wss://<your-container>.adom.cloud/proxy/8765/", "auto_connect": true, "enabled": true}

The paste box (since 1.9.43) also accepts the full export wrapper {"servers":[...]} or even a bare wss://... URL, and shows an error toast instead of failing silently.

The zero-JSON path (preferred since 1.9.42): sign in to Adom inside AD (Connections shows a "Sign in to Adom" button when signed out). AD then pulls your containers' relays from your account automatically, no JSON at all, and connects immediately.

For the Hydrogen container side: adom-desktop targets lists what is connected, and the discovery skill (adom-wiki pkg install adom/adom-desktop) documents the shape. If Claude still struggles after a sign-in, tell me what it tried to paste and I will turn that into an accepted format.

John Lauer · 17d ago

Fixed in 1.9.171 — the AI no longer has to guess (or even paste) the JSON.

What changed:

One command emits everything: adom-desktop setup_desktop (aliases: connect, setup, connect_info) auto-detects the container's relay URL and returns the exact connection config. The AI's likely guesses now all land on it, and the no-desktops-connected response points at it too — so the hand-built-JSON failure mode is gone.
Better: zero paste on the common path. setup_desktop now leads with a ready-to-run register_command — adom-desktop register_container with the name + URL filled in. Running it injects the connection into the user's Adom account, so when they install Adom Desktop and sign in with their Adom account, the connection just appears in their list and auto-connects. No JSON at all.
Paste-JSON survives only as the fallback (non-Adom box, or a user who won't sign in), and even then the AI pastes the emitted server_config verbatim instead of assembling one.

The skills (adom-desktop + adom-desktop-discovery) teach this flow now, so Hydrogen/Claude should get it right first try. Container side: adom-wiki pkg update, verify adom-desktop --version >= 1.9.171.