app

Adom Bridge

Public Made by Adom

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

adom-bridgetauriclaude-codebridgekicadfusion360puppeteerdesktop-automation
Overview Files Skills Discover Packages Releases Dependencies Issues19 Breadcrumbs Pull Requests1 Activity
Closed feature request

Connections panel needs a Refresh button (re-sync cloud servers + re-dial relays on demand)

kaleymer · 3mo ago ·closed by John Lauer

Feature request: a Refresh button on the relay Connections panel

The Connections panel has no way to manually re-sync/re-dial the relay connections. Today the workarounds are restarting ab or waiting for the supervisor/boot-time cloud sync to come around, which is slow and opaque during setup.

The setup scenario that motivates this

While connecting a cloud container ("Cosmiic") to a laptop today:

  1. The container side registered via register_container and started the relay (adom-bridge-cli serve --supervise).
  2. On the laptop, there was no obvious way to say "check again now" — no button to re-pull cloud-discovered servers (desktop.container.*) or force reconnection attempts on existing entries.
  3. From the cloud side, adom-bridge-cli targets stays empty with no way to nudge the desktop other than asking the user to restart the app.

Ask

A Refresh button on the Connections panel that, in one click:

  • Re-pulls cloud-discovered servers from the signed-in account (same as the boot-time sync_cloud_servers_now), and
  • Immediately re-attempts connection on all enabled entries (rather than waiting for the next supervisor tick).

Nice-to-have: a matching relay-side/CLI verb (e.g. connections_refresh) so an AI walking a user through setup can trigger the same re-sync remotely.

3 Replies

John Lauer · 3mo ago

Shipped in ab 2.0.25: a Refresh button (the circular-arrow control) on the Connections panel header, next to Connect All. One click re-pulls your cloud-discovered servers (desktop.container.*) AND re-dials every enabled relay immediately, no restart and no waiting for the supervisor/boot sync. It works signed-out too (it still re-dials the local entries; there is just no cloud to pull). The button spins while it runs and the Activity Log reports how many cloud servers merged.

Under the hood it calls the same sync_cloud_servers_now + immediate-connect path that the post-sign-in and hourly syncs use, so it is the exact "check again now" you wanted during a container onboarding.

Two things for the specific setup flow you described:

  1. The cloud-side half already has a lever: adom-bridge-cli server_sync (optionally --target ) makes a signed-in desktop re-read its cloud profile RIGHT NOW from the container side, so a container that just ran register_container can nudge the desktop without the human touching anything. The new button is the human-facing equivalent of the same operation.

  2. On adom-bridge-cli targets staying empty from the container: that is a relay-connection question, not a cloud-sync one (targets lists who is connected to the relay, which the Refresh button now helps by re-dialing). If the desktop is dialed in but targets is still empty, that is worth its own issue with the relay URL both sides are using.

John Lauer · 3mo ago

Shipped in ab 2.0.25: a Refresh button (the circular-arrow control) on the Connections panel header, next to Connect All. One click re-pulls your cloud-discovered servers (desktop.container.*) AND re-dials every enabled relay immediately, no restart and no waiting for the supervisor/boot sync. It works signed-out too (it still re-dials the local entries; there is just no cloud to pull). The button spins while it runs and the Activity Log reports how many cloud servers merged.

Under the hood it calls the same sync_cloud_servers_now + immediate-connect path that the post-sign-in and hourly syncs use, so it is the exact "check again now" you wanted during a container onboarding.

Two things for the specific setup flow you described:

  1. The cloud-side half already has a lever: adom-bridge-cli server_sync (optionally --target ) makes a signed-in desktop re-read its cloud profile RIGHT NOW from the container side, so a container that just ran register_container can nudge the desktop without the human touching anything. The new button is the human-facing equivalent of the same operation.

  2. On adom-bridge-cli targets staying empty from the container: that is a relay-connection question, not a cloud-sync one (targets lists who is connected to the relay, which the Refresh button now helps by re-dialing). If the desktop is dialed in but targets is still empty, that is worth its own issue with the relay URL both sides are using.

John Lauer · 2mo ago

Shipped. The Connections panel has a Refresh button (btn-refresh-conn, the circular-arrow control) that re-pulls your cloud servers (sync_cloud_servers_now) and re-dials every relay immediately, no restart. Closing.

John Lauer closed this · 2mo ago

Log in to reply.