adom-bridge-cli.exe desktop_list_windows
adom-bridge-cli.exe desktop_screenshot_window '{"titleContains": "Notepad"}'
adom-bridge-cli.exe notify_user '{"title":"Done","body":"Notepad screenshot saved"}'

adom-bridge-cli.exe commands

adom-bridge-cli.exe ping

"%LOCALAPPDATA%\Adom Bridge\adom-bridge-cli.exe" ping

# Using Adom Bridge from a local AI (Claude Desktop, Claude Code, Codex)

You do not need the cloud to use Adom Bridge. Install Adom Bridge on your PC, and any
AI tool running on that same PC can immediately drive your machine: take
screenshots, list and capture windows, launch apps, show you notifications,
run commands. No relay, no container, no account wiring on the AI side.

![Adom Bridge running on the PC](main-view.png)

This page covers the local path. Driving your desktop from a cloud container
over the relay is a separate setup, documented in the main README and the
`adom-bridge` skill.

## What the installer sets up

When you run the signed Windows installer:

- The GUI installs to `%LOCALAPPDATA%\Adom Bridge\` and starts on login.
- A command-line tool, `adom-bridge-cli.exe`, is installed next to the GUI,
  and that folder is added to your user PATH. Any local program can call it
  by name from a fresh shell.
- Adom Bridge's consumer skills (the documentation an AI agent reads to learn the
  verbs) are linked into your agents automatically. On every launch, Adom Bridge
  copies its bundled skills into both `~/.claude/skills/` (Claude Desktop and
  Claude Code) and `~/.codex/skills/` (Codex).

So the moment Adom Bridge is installed and running, a local Claude or Codex session
already knows what Adom Bridge can do and how to call it.

## How the skill auto-link works

Each skill Adom Bridge installs lives in its own folder, for example
`~/.claude/skills/adom-bridge/`, and contains a small marker file named
`.adom-managed`. The marker means "Adom Bridge owns this folder":

- On every Adom Bridge launch, each managed skill is refreshed if the bundled copy
  changed (which happens when Adom Bridge upgrades itself). Unchanged skills are left
  alone, so a normal launch writes nothing.
- If you made your own skill with the same folder name, Adom Bridge sees there is no
  marker and never touches it.
- Deleting the `.adom-managed` marker from a folder stops Adom Bridge from updating
  that skill. Your edits to it become permanent.
- To turn the whole feature off, launch Adom Bridge with the environment variable
  `ADOM_SKILLS_LINK=0`.

## A worked example

Say you are in Claude Code on your PC and you ask:

> "Grab a screenshot of my Notepad window and let me know when it's saved."

The agent, having the Adom Bridge skills, would run something like:

```
adom-bridge-cli.exe desktop_list_windows
adom-bridge-cli.exe desktop_screenshot_window '{"titleContains": "Notepad"}'
adom-bridge-cli.exe notify_user '{"title":"Done","body":"Notepad screenshot saved"}'
```

The first call finds the window, the second captures it as a lossless PNG
(window chrome included), and the third pops a Windows toast so you see the
result even if the agent's console is buried. Every call goes straight to the
running Adom Bridge GUI over loopback (`127.0.0.1`); nothing leaves your machine.

To see everything available:

```
adom-bridge-cli.exe commands
```

## Troubleshooting

**Is Adom Bridge running?** Look for the Adom Bridge tray icon, or open the window
from the Start Menu. The window title shows the running version. If Adom Bridge is
closed to the tray it is still serving; closing the window does not stop it.

**Quick liveness check:**

```
adom-bridge-cli.exe ping
```

A healthy Adom Bridge answers immediately. If ping fails, launch Adom Bridge from
the Start Menu and try again.

**`adom-bridge-cli.exe` is not recognized.** The installer adds
`%LOCALAPPDATA%\Adom Bridge\` to your PATH, but shells that were already
open before the install do not see the change. Open a new terminal, or call
it by full path:

```
"%LOCALAPPDATA%\Adom Bridge\adom-bridge-cli.exe" ping
```

**The skills did not appear in my agent.** They are linked when Adom Bridge launches,
so start (or restart) Adom Bridge, then check for folders like
`~/.claude/skills/adom-bridge/`. If you set `ADOM_SKILLS_LINK=0`, the link
is disabled.

## Related docs

- `skills/LOCAL_AI.md`: the agent-facing version of this page.
- `skills/DIRECT_API.md`: the loopback HTTP API, for apps that want to call
  Adom Bridge without spawning the CLI.
- `README.md`, "How it works" and "Install": the full picture, including the
  cloud-relay path.