web-bridge

# Web Bridge — Browser Automation via CDP Control a real Chrome/Edge browser from the AI agent. **No extension installation needed.** All data stays local. ## Quick Start ### Start the bridge server (one command) ```bash node ~/.coderix/skills/web-bridge/bridge-server.cjs ``` The server auto-detects Chrome/Edge, launches it with remote debugging, and listens on port **9223**. You'll see `BRIDGE_READY port=9223` when ready. If Chrome is already running with `--remote-debugging-port=9222`, the server connects to it instead of launching a new one. ### Make a request ```bash curl -s -X POST http://127.0.0.1:9223/cmd \ -H 'Content-Type: application/json' \ -d '{"action":"navigate","params":{"url":"https://example.com"}}' ``` All commands go to `POST /cmd` with JSON body `{"action":"...", "params":{...}}`. ### Sessions Add `"session":"name"` to the request body to isolate tabs for multi-task workflows. Each session tracks its own set of tabs. ```bash # Start a task in its own session curl -s -X POST http://127.0.0.1:9223/cmd \ -d '{"action":"navigate","params":{"url":"https://example.com","new_tab":true},"session":"research"}' # Later actions in the same session automatically use the right tab curl -s -X POST http://127.0.0.1:9223/cmd \ -d '{"action":"snapshot","session":"research"}' # Close all tabs in a session when done (session name optional if active) curl -s -X POST http://127.0.0.1:9223/cmd \ -d '{"action":"close_session","session":"research"}' # Or ...