Connecting with hydrogen container

by adom

Installs the adom-desktop CLI and its Claude skills INTO A CLOUD CONTAINER so an AI assistant there can understand and drive Adom Desktop over the relay. This is the container side, NOT the app itself. The Adom Desktop app is the signed Windows installer under Download below: run THAT on the PC you want the AI to control. Rule of thumb: pkg install here (in your Linux container), Download there (on your Windows PC). Once installed, the AI can drive file transfer, screenshots, notifications, KiCa

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

Open bug report

kaleymer · 12d ago

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.

1 Reply

John Lauer · 6d 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.