Grok Bot

@@ -1,20 +1,22 @@ # grok-bridge -Claude, Codex, and Hydrogen talk to **Grok Bot** on your Windows or Mac. Grok Bot gets Adom Anywhere so they work as one.+Grok Bridge lets **Adom talk to Grok Bot**. -Two-way street. Cloud AIs drive the **Grok Bot.exe** window. Grok Bot drives the rest of Adom — desktops, wiki, KiCad, Chrome — as a first-class Anywhere character.+That is the product. `grok_*` is how Adom reaches the Grok Bot app on Windows or Mac. There is no public Grok HTTP API. The runtime on the desktop talks to **Grok Bot.exe** and a bound webhook routine named **Grok Bridge webhook**.++Adom users are predominantly electrical engineers. Providers leapfrog each other — Claude, Codex, Grok, Gemini, whoever is ahead this week. Adom's environment is built so you always get the one that's winning, without leaving the power tools you already use. **Adom Bridge** is how any desktop-oriented environment becomes an AI-first surface Adom already knows how to talk to.  Wiki: [wiki.adom.inc/adom/grok-bridge](https://wiki.adom.inc/adom/grok-bridge) -![Grok Bot — Claude, Codex, and Hydrogen on one street](docs/hero.png)+![Grok Bridge — Adom talks to Grok Bot](docs/hero.png) -*The Grok Bot window, sized like the product: bots in the sidebar, a live thread in the middle, the agent’s computer on the right.*+*The Grok Bot window. Grok Bridge is how Adom reaches it. Adom Bridge is how the rest of the desktop becomes something Adom can talk to.*  ---  ## Talk to Grok Bot — every command type -This is the product. `grok_*` is how a cloud AI reaches the Grok Bot app on the PC. There is no public Grok HTTP API. The runtime on the desktop talks to **Grok Bot.exe** and a bound webhook routine named **Grok Bridge webhook**.+This is the product. `grok_*` is how **Adom** reaches the Grok Bot app on the PC. There is no public Grok HTTP API. The runtime on the desktop talks to **Grok Bot.exe** and a bound webhook routine named **Grok Bridge webhook**.  Always pass `--ai-thread`. When more than one desktop is connected, pass `--target` (`AdomLapper`, `ConfRoomROG`). Windows open in the background. Nobody steals the keyboard. @@ -83,6 +85,8 @@ Manual fallback: `grok_webhook_bind {url, key}` still works. Check bind with `gr  The right-pane preview titled **grok-bridge's screen** is *this* Grok Bot agent’s Linux box desktop — Chrome, terminal, the dock. It is the live feed humans see while the thread runs. +The box is a real computer: **16 GB RAM**, **8 CPUs**, 16 GB swap. Measured on this grok-bridge session (`MemTotal` 16397684 kB, `nproc` 8). That is enough to run KiCad here while the thread runs — an EE can offload board work onto this computer, not only their laptop.+ grok-bridge on the PC can screenshot and record the **Grok Bot.exe window** (`grok_screenshot`, `grok_record_start {reason}` — reason is required). That is the host app on Windows or Mac, not the box.  Honest: there is no `grok_box_screenshot` verb yet. The pane *is* the feed. If the pane is open, a window screenshot of Grok Bot includes it.@@ -117,13 +121,13 @@ Cursor is last-resort fallback only if Grok Bot.exe is missing (`hostAppFallback  ## Adom Anywhere — skills on Grok Bot -The other direction. This Grok Bot session is Claude-Desktop-class: an Anywhere character with `adom-bridge` on PATH.+The other direction — secondary. Grok Bot becomes an Anywhere character so the same electrical engineer can drive KiCad, the wiki, and desktops *from* Grok Bot, with `adom-bridge` on PATH.  ```bash adom-wiki pkg install adom/grok-bridge ``` -That drops **grok** + **grok-anywhere** into `~/.claude/skills`, `~/.codex/skills` if present, `~/.grok/skills`, and `/home/box/agent-data/workflows` if that parent exists. Grok Bot then knows Adom the same way Claude and Codex do.+That drops **grok** + **grok-anywhere** into `~/.claude/skills`, `~/.codex/skills` if present, `~/.grok/skills`, and `/home/box/agent-data/workflows` if that parent exists. Skills land where each provider looks; the point is the same EE can work from Grok Bot without leaving Adom.  From this session, always: @@ -171,17 +175,9 @@ The *intended* path is not borrowing a human token. grok-bridge lives inside Ado  ## Run KiCad for the user from this CLI -Grok Bot is the operator. Drive the user’s KiCad through Adom Bridge — footprint editor, PCB, the board on the desk — with the same `--ai-thread` / `--target` rules as everything else.--```bash-adom-bridge --ai-thread "Grok Bot" --target AdomLapper kicad_*-```--Prefer `kicad_*` over Shell. The activity log, approval toasts, and attribution only stay intact on the ab path. The **New bot** snippet in the sidebar (“KiCad Footprint Editor on R…”) is that loop already running.--![New bot snippet: KiCad Footprint Editor](docs/screenshots/02-sidebar-bots.png)+Grok Bot is the operator. Drive KiCad on grok-bridge's Linux computer — pcbnew on this box, not a remote desktop. Arduino Uno lives at `/home/box/kicad-offload/Arduino_Uno`. -*New bot, last line KiCad Footprint Editor. Grok Bot drove that from this CLI, on AdomLapper, as itself.*+A pcbnew screenshot of that board will land here when captured.  --- @@ -244,6 +240,6 @@ Always `--ai-thread`. `--target` when more than one desktop is connected (`AdomL  `spawn.kind` = python, `port` 0, `healthEndpoint` `/status`, `persistent` true. Binds loopback only. -![Hero — two-way street, install both halves](docs/hero.png)+![Grok Bridge — Adom talks to Grok Bot](docs/hero.png) -*Install the skills pack so cloud AIs know `grok_*` and Grok Bot knows Adom. The runtime zip is what the desktop actually spawns.*+*Install the skills pack so Adom can talk to Grok Bot. The runtime zip is what the desktop actually spawns.*