Bridge Server

The always-on service that keeps kbcode connected to your browser — one background process, every Chrome profile at once.

Chrome automation needs a live connection between kbcode and your browser. The Bridge Server is that connection — a single WebSocket relay that lets every Chrome profile connect to kbcode at once, routes commands to the right profile, and stays running in the background, even when kbcode isn't open.

Install it once and it just works. No console window, no per-session setup, nothing to type at each launch. It registers as a Windows service that starts on boot and survives reboots.

✓ Works with kbcode out of the box.
Install the Bridge Server once, then use the browser_* tools in any kbcode session. The Chrome extension connects automatically — one port (ws://127.0.0.1:8767), every profile routed by account.

Download

⬇ Download bridge-server-setup.exe

Windows 10/11. One self-contained installer — bundles the browser extension plus the service, nothing else to install.

1. Install

Run bridge-server-setup.exe and click through the installer. It places the Bridge Server under Program Files\kbcode\Bridge Server, registers it as a Windows service and starts it — no admin shell, no PATH edits.

2. Use it from kbcode

Inside any kbcode session, browser automation just works. The bridge is already running on localhost:8767 — kbcode connects to it as a tool client and the Chrome extension relays commands.

Check it's running

bridge-server.exe status

Shows Daemon RUNNING (pid …, port 8767) or that it isn't running.

Browse your profiles

kb bridge status

From kbcode, lists every connected Chrome profile and the bridge state.

Stop or start the service

bridge-server.exe stop

Stops the running daemon. Start it again with bridge-server.exe install (auto-start at login) or bridge-server.exe start (foreground, for testing).

3. Command reference

Command	What it does
`bridge-server.exe status`	Show daemon liveness + connections
`bridge-server.exe install`	Install as a Windows scheduled task (auto-start at login)
`bridge-server.exe install-service`	Install as a Windows service (recommended, runs 24/7)
`bridge-server.exe start`	Start in the foreground (testing only)
`bridge-server.exe stop`	Stop a running daemon
`bridge-server.exe uninstall`	Remove the scheduled task / service
`bridge-server.exe --version`	Print the version

4. Command reference (kbcode)

The installed kb CLI exposes bridge management too:

Command	What it does
`kb bridge status`	Bridge state + every connected profile
`kb bridge doctor`	Run the bridge diagnostic
`kb extension`	Open the Chrome Web Store page to install the extension

5. Troubleshooting

"Bridge is not listening." Confirm the service is running: bridge-server.exe status. Restart it with bridge-server.exe install-service.
Port 8767 in use. Find the conflicting process with netstat -ano | findstr :8767, then either free the port or change the bridge port in the installer config.
No Chrome profiles connect. Make sure the kbcode Chrome extension is installed and signed in — run kb extension to open it.

← Back to docs