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

Download

Connectivity verbs

Liveness, status, multi-AD targeting.

Part of the Adom Desktop verb reference. Invoke as adom-desktop <verb> '<json>'.

`health`

Check if the relay server HTTP API is reachable

Returns: Relay server health status

`kick_all`

Force-disconnect all WebSocket clients (they auto-reconnect in ~5s)

Note: Use when connections are stale or duplicated

`ping`

Round-trip connectivity test (5s timeout)

Args:

message — optional string, echoed back

Returns: echo, roundTripMs, status

Note: Always run this first to verify desktop connection

`status`

Query connected clients, capabilities, and app installation status

Returns: clients count, appName, hostname, capabilities[], desktop app status (kicad/fusion/browser installed/running)

`targets`

v1.8.133+: list the Adom Desktops connected to this relay so you can address one by name. Each AD has a name (its --client-name / Settings value, defaulting to the OS hostname). Use this to discover names, then run any verb with the global --target selector, or --target all to fan out to every AD.

Returns: {count, targets:[{name, hostname, version, os, connectedAt}], _hint}

Note: See _targeting_note at the top of this map for how --target works.

# Connectivity verbs

Liveness, status, multi-AD targeting.

_Part of the [Adom Desktop verb reference](VERB-REFERENCE.md). Invoke as `adom-desktop <verb> '<json>'`._

### `health`

Check if the relay server HTTP API is reachable

**Returns:** Relay server health status


### `kick_all`

Force-disconnect all WebSocket clients (they auto-reconnect in ~5s)

**Note:** Use when connections are stale or duplicated


### `ping`

Round-trip connectivity test (5s timeout)

**Args:**
  - `message` — optional string, echoed back

**Returns:** echo, roundTripMs, status

**Note:** Always run this first to verify desktop connection


### `status`

Query connected clients, capabilities, and app installation status

**Returns:** clients count, appName, hostname, capabilities[], desktop app status (kicad/fusion/browser installed/running)


### `targets`

v1.8.133+: list the Adom Desktops connected to this relay so you can address one by name. Each AD has a name (its --client-name / Settings value, defaulting to the OS hostname). Use this to discover names, then run any verb with the global --target <name> selector, or --target all to fan out to every AD.

**Returns:** {count, targets:[{name, hostname, version, os, connectedAt}], _hint}

**Note:** See _targeting_note at the top of this map for how --target works.