Adom Bridge - Commit

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 Issues20 Breadcrumbs Pull Requests1 Activity

← Commit history

Publish 1.8.182

barrett-land ·edaec205f5 ·4mo ago ·parent 11be5b2

4 files changed +16−2

SKILL.md+7 package.json+1−1 page.json+1−1 skills/adom-desktop/SKILL.md+7

SKILL.md+7

@@ -153,6 +153,13 @@ curl -sf http://127.0.0.1:8766/health  **You are running on a Docker container. You have NO access to the user's desktop.** Guide them step-by-step, ask questions, wait for answers, and verify each step. +> **⚠ ALWAYS give the config for the CURRENT container — and make sure the relay is up first.**+>+> When the user asks for "the copy-paste", "the server config", "the JSON", or anything similar:+> 1. **Source of truth is `adom-desktop setup_desktop`** — its `server_config` field is the ready-to-paste JSON, derived from *this* container's own relay URL.+> 2. **NEVER read the config out of `hydrogen_preferences`** (`adom-cli carbon user get` → `settings["desktop.container.*"]`). Those entries can be for *other* containers (e.g. a `dashboard` entry while the user is in `newdash`) and will be wrong. The current container's identity comes from its own `VSCODE_PROXY_URI` env var (`https://<host>/proxy/{{port}}/` → relay `wss://<host>/proxy/8765/`).+> 3. **Before handing over the config or claiming "connected", verify the relay service is actually running on your end** so the `…/proxy/8765/` URL doesn't return a **500** (500 = proxy has no upstream = relay not running). Probe `curl -sf http://127.0.0.1:8766/health` (note: `ss`/`netstat` may not see in-container sockets — probe with curl), and if it's down, `adom-desktop serve &` and re-check before proceeding.+ ### Step 1: Check if already connected  ```bash

package.json+1−1

@@ -1,6 +1,6 @@ {   "slug": "adom-desktop",-  "version": "1.8.181",+  "version": "1.8.182",   "type": "app",   "hero": { "path": "docs/hero.png" },   "description": "Laptop bridge: file transfer, screenshots, notifications, KiCad + Fusion 360 control, real-Chrome (Puppeteer) automation, and Hydrogen Desktop proxy. One install gives Claude every desktop verb it needs.",

page.json+1−1

@@ -1,6 +1,6 @@ {   "slug": "adom-desktop",-  "version": "1.8.181",+  "version": "1.8.182",   "type": "app",   "description": "Laptop bridge: file transfer, screenshots, notifications, KiCad + Fusion 360 control, real-Chrome (Puppeteer) automation, and Hydrogen Desktop proxy. One install gives Claude every desktop verb it needs.",   "keywords": [

skills/adom-desktop/SKILL.md+7

@@ -153,6 +153,13 @@ curl -sf http://127.0.0.1:8766/health  **You are running on a Docker container. You have NO access to the user's desktop.** Guide them step-by-step, ask questions, wait for answers, and verify each step. +> **⚠ ALWAYS give the config for the CURRENT container — and make sure the relay is up first.**+>+> When the user asks for "the copy-paste", "the server config", "the JSON", or anything similar:+> 1. **Source of truth is `adom-desktop setup_desktop`** — its `server_config` field is the ready-to-paste JSON, derived from *this* container's own relay URL.+> 2. **NEVER read the config out of `hydrogen_preferences`** (`adom-cli carbon user get` → `settings["desktop.container.*"]`). Those entries can be for *other* containers (e.g. a `dashboard` entry while the user is in `newdash`) and will be wrong. The current container's identity comes from its own `VSCODE_PROXY_URI` env var (`https://<host>/proxy/{{port}}/` → relay `wss://<host>/proxy/8765/`).+> 3. **Before handing over the config or claiming "connected", verify the relay service is actually running on your end** so the `…/proxy/8765/` URL doesn't return a **500** (500 = proxy has no upstream = relay not running). Probe `curl -sf http://127.0.0.1:8766/health` (note: `ss`/`netstat` may not see in-container sockets — probe with curl), and if it's down, `adom-desktop serve &` and re-check before proceeding.+ ### Step 1: Check if already connected  ```bash