# Adom Anywhere: use Adom from Claude Desktop or Codex

You do not need the cloud, and you do not need to be an Adom container user. If you already run Claude Desktop, Claude Code, or Codex on your PC, installing Adom Bridge makes your agent a full Adom ecosystem citizen. This page is the complete story; the short version lives on the main page.

## What your agent can do, locally, today

- **Drive the PC.** Screenshots, windows, files, shell (human-approved), notifications, KiCad, Fusion 360: all local, no relay, no setup. See [local-ai.md](local-ai.md) for the routing model.
- **Automate a real browser.** The bundled pup bridge gives your agent multi-session Chrome automation out of the box.
- **Author the wiki.** Create and manage pages, files, discussions, and packages on wiki.adom.inc with the account you signed in with.
- **Reach into your Hydrogen workspace.** Open webview panels, drive sandboxes, and query the workspace layout in your cloud Hydrogen container, from the local PC.
- **Stay current automatically.** Skills refresh themselves; nothing to maintain.

## What exactly gets installed

The one signed installer puts everything in `%LOCALAPPDATA%\Adom Bridge` and adds it to your user PATH:

| Piece | What it is |
|---|---|
| `adom-bridge.exe` | The app itself (tray, approvals, bridges) |
| `adom-bridge-cli.exe` | The command surface your agent calls: every desktop verb |
| `adom-wiki.exe` | The full Adom Wiki CLI (pages, files, discussions, packages, releases) |
| `adom-cli.exe` | The Adom platform CLI: identity, containers, and the Hydrogen workspace family (webview, workspace, sandbox, screenshot) |
| Skills, auto-linked | Adom Bridge's own skill set is copied into `~/.claude/skills` and `~/.codex/skills` on every launch, and the wider ecosystem skill packages (the adom core set, the adom-wiki CLI skill) are fetched from their wiki packages and refreshed daily. Marker files (`.adom-managed`) guarantee your own skills are never touched. |

## How the CLIs work on Windows

All three CLIs are native Windows executables; there is no WSL, container, or runtime prerequisite.

- `adom-bridge-cli.exe` talks to the running app over a loopback-only API and needs zero configuration.
- `adom-wiki.exe` authenticates with the account you signed in to Adom Bridge with: run wiki commands through `adom-bridge-cli wiki_exec` and the token is injected automatically, or set `ADOM_WIKI_TOKEN` for direct calls.
- `adom-cli.exe` has its token seeded automatically: Adom Bridge writes your signed-in session token into adom-cli's config at sign-in and refreshes it daily. For the Hydrogen workspace verbs, target a container by setting `VSCODE_PROXY_URI` to its cloud URL (`https://<container-host>.adom.cloud/proxy/{{port}}/`).

## Skills written for containers, translated for Windows

The ecosystem skills were written for agents living inside Adom Linux containers, so delivering them verbatim would hand a local agent instructions that misfire (bash examples, container paths). Adom Bridge therefore stamps every delivered ecosystem skill with an ADOM ANYWHERE NOTE banner classifying how it applies on your machine (as-is, adapted, or container-only), and ships a dedicated translation skill (`adom-bridge-anywhere-windows`) with the full table: what changes, what works natively, and what genuinely needs a container.

## The one boundary, and the answer

A local agent cannot RUN the Linux binaries that many wiki packages publish. Those need an Adom Linux container, and that is exactly what **[Adom Hydrogen](https://wiki.adom.inc/adom/hydrogen)** provides: a full containerized AI workspace on the same PC that pairs with the Adom Bridge you already installed. When your agent hits that boundary, Hydrogen is the answer.