app
Adom Bridge
Public Made by Adomby 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
← Commit history
docs/presence.md+103−103@@ -1,103 +1,103 @@-# Adom Desktop in the background: the tray, the hidden window, and the taskbar tile - -Adom Desktop is built to live quietly on your machine. Most of the time its -window is hidden and it sits in the system tray, still connected and still -serving, while costing very little. This page explains what closing the window -really does, why that is cheap, how to read AD's mode from the taskbar alone, -and how to actually exit. - - - - -## What closing the window really does - -Clicking the X on AD's window hides the window. It does not exit the app. AD -keeps running in the background: it stays connected to your relay, keeps its -bridges alive, and can still show notifications and approval prompts. That is -the point of the app; it is the always-reachable agent surface for your -machine, so "close" means "get out of my way", not "stop working". - -You will not be left guessing. The first three times you close the window, AD -shows a notification explaining that it moved to the tray. After that it -assumes you know and stays quiet. - -If you launch AD again while it is hidden, the existing instance simply shows -and focuses its window (there is never a second copy running). - -## Why AD in the tray costs very little - -AD is two things: a small native core process that does all the real work -(roughly 60 MB), and a web-technology window (WebView2) that only exists to -paint the user interface. - -When the window is hidden, that UI layer is suspended: its renderer is marked -invisible, its memory target is dropped to low, and the page itself is put to -sleep. GPU compositing for the hidden UI is switched off as well. Work that -exists only to paint the screen (like the little health LEDs) is skipped -entirely while nothing is visible. - -The native core is not throttled at all. Connections, bridges, notifications, -and approvals run at full speed whether the window is visible or not. - -When you open the window again, the UI wakes up immediately and returns to -full power. Status LEDs refresh themselves within about 15 seconds of the -window appearing. - -## Reading the mode from the taskbar tile - -AD runs in one of two modes, and the taskbar button tells you which without -opening anything: - -- A MUTED teal tile named "Adom Desktop": AD is running standalone, on its - own. This is the default for a normal install. -- A VIVID teal tile named "Adom Desktop HD Embedded": Hydrogen Desktop - launched AD and is driving its lifecycle. - -The swap is live: when the mode changes, the button's tile and name change -within about a second, with no restart and no flicker. Under the hood each -mode is a separate registered Windows app identity, and the window switches -between them. - -Two things to know: - -- A taskbar pin belongs to one identity. If you pin AD in one mode, the - running window shows as a separate button whenever AD is in the other mode. -- The tray icon exists only in standalone mode. When AD is embedded in - Hydrogen Desktop, the tray icon is hidden, so the taskbar tile is the way - to tell the modes apart. - -The window title is also informative: it shows the running version, whether -the build is signed, and a HOST or SANDBOX marker. - -## Launch on boot - -AD starts on login by default. The setting is a checkbox in Settings (checked -by default), and AD keeps the actual Startup entry in sync with it on every -launch: if the checkbox is on and the Startup shortcut is missing, AD -recreates it; if the checkbox is off, AD removes it. - -To turn it off, untick the launch-on-boot checkbox in Settings. If you have -disabled Adom Desktop under Task Manager's Startup apps instead, AD respects -that choice and does not re-enable itself. - -## How to actually exit AD - -Closing the window never exits. The supported way to stop AD is the shutdown -command, for example from the CLI: - - adom-desktop desktop_shutdown - -or over the local API: - - curl -s -X POST 127.0.0.1:47200/command -d '{"command":"shutdown"}' - -With launch on boot enabled, AD will come back at the next login; untick the -Settings checkbox first if you want it to stay off. - -One more lifecycle note: if Hydrogen Desktop dies while AD is embedded, AD -does not die with it. It reverts to standalone mode (tray icon back, -connections preserved) so the machine stays reachable. - -## Updates never steal your focus - -When Adom Desktop restarts itself to apply an automatic update, it comes back in the tray without showing or focusing the window. A window that appears in front of you always has a reason, and the Activity Log records it (look for foreground entries naming who asked and why). +# Adom Desktop in the background: the tray, the hidden window, and the taskbar tile++Adom Desktop is built to live quietly on your machine. Most of the time its+window is hidden and it sits in the system tray, still connected and still+serving, while costing very little. This page explains what closing the window+really does, why that is cheap, how to read AD's mode from the taskbar alone,+and how to actually exit.+++++## What closing the window really does++Clicking the X on AD's window hides the window. It does not exit the app. AD+keeps running in the background: it stays connected to your relay, keeps its+bridges alive, and can still show notifications and approval prompts. That is+the point of the app; it is the always-reachable agent surface for your+machine, so "close" means "get out of my way", not "stop working".++You will not be left guessing. The first three times you close the window, AD+shows a notification explaining that it moved to the tray. After that it+assumes you know and stays quiet.++If you launch AD again while it is hidden, the existing instance simply shows+and focuses its window (there is never a second copy running).++## Why AD in the tray costs very little++AD is two things: a small native core process that does all the real work+(roughly 60 MB), and a web-technology window (WebView2) that only exists to+paint the user interface.++When the window is hidden, that UI layer is suspended: its renderer is marked+invisible, its memory target is dropped to low, and the page itself is put to+sleep. GPU compositing for the hidden UI is switched off as well. Work that+exists only to paint the screen (like the little health LEDs) is skipped+entirely while nothing is visible.++The native core is not throttled at all. Connections, bridges, notifications,+and approvals run at full speed whether the window is visible or not.++When you open the window again, the UI wakes up immediately and returns to+full power. Status LEDs refresh themselves within about 15 seconds of the+window appearing.++## Reading the mode from the taskbar tile++AD runs in one of two modes, and the taskbar button tells you which without+opening anything:++- A MUTED teal tile named "Adom Desktop": AD is running standalone, on its+ own. This is the default for a normal install.+- A VIVID teal tile named "Adom Desktop Hydrogen Embedded": Hydrogen Desktop+ launched AD and is driving its lifecycle.++The swap is live: when the mode changes, the button's tile and name change+within about a second, with no restart and no flicker. Under the hood each+mode is a separate registered Windows app identity, and the window switches+between them.++Two things to know:++- A taskbar pin belongs to one identity. If you pin AD in one mode, the+ running window shows as a separate button whenever AD is in the other mode.+- The tray icon exists only in standalone mode. When AD is embedded in+ Hydrogen Desktop, the tray icon is hidden, so the taskbar tile is the way+ to tell the modes apart.++The window title is also informative: it shows the running version, whether+the build is signed, and a HOST or SANDBOX marker.++## Launch on boot++AD starts on login by default. The setting is a checkbox in Settings (checked+by default), and AD keeps the actual Startup entry in sync with it on every+launch: if the checkbox is on and the Startup shortcut is missing, AD+recreates it; if the checkbox is off, AD removes it.++To turn it off, untick the launch-on-boot checkbox in Settings. If you have+disabled Adom Desktop under Task Manager's Startup apps instead, AD respects+that choice and does not re-enable itself.++## How to actually exit AD++Closing the window never exits. The supported way to stop AD is the shutdown+command, for example from the CLI:++ adom-desktop desktop_shutdown++or over the local API:++ curl -s -X POST 127.0.0.1:47200/command -d '{"command":"shutdown"}'++With launch on boot enabled, AD will come back at the next login; untick the+Settings checkbox first if you want it to stay off.++One more lifecycle note: if Hydrogen Desktop dies while AD is embedded, AD+does not die with it. It reverts to standalone mode (tray icon back,+connections preserved) so the machine stays reachable.++## Updates never steal your focus++When Adom Desktop restarts itself to apply an automatic update, it comes back in the tray without showing or focusing the window. A window that appears in front of you always has a reason, and the Activity Log records it (look for foreground entries naming who asked and why).