[codex] Add generic browser pool and rbc list

Cargo.toml

@@ -28,6 +28,10 @@ tungstenite = "0.24"
 name = "browser-connection"
 path = "src/bin/browser-connection.rs"
 
+[[bin]]
+name = "browser-connection-relay"
+path = "src/bin/browser-connection-relay.rs"
+
 [dev-dependencies]
 tempfile = "=3.10.1"
 proptest = "=1.4.0"

README.md

@@ -13,6 +13,7 @@ Installs two binaries:
 ```text
 docker-git-browser-connection  # start/status browser container
 browser-connection             # MCP stdio server for Codex/Hermes
+browser-connection-relay       # WebSocket relay for browser share links
 ```
 
 ## Start browser manually
@@ -46,6 +47,116 @@ args = ["--project", "dg-my-project"]
 ```
 
 Use `browser-connection`, not `npx @playwright/mcp`. The MCP server starts/reuses the same Rust-managed browser container automatically.
+It also starts a local browser/noVNC control panel by default; `browser_list` reports its
+`controlPanelUrl`.
+
+Optional panel controls:
+
+```toml
+[mcp_servers.playwright]
+command = "browser-connection"
+args = ["--project", "dg-my-project", "--control-port", "6888"]
+```
+
+Use `--no-control-panel` for headless tests or when another process owns the chosen port.
+
+## Share a remote Edge by link
+
+For a remote Microsoft Edge where you do not want SSH, VPN, or an exposed CDP port, use the Edge
+share extension plus the relay:
+
+```bash
+browser-connection-relay --bind 127.0.0.1:8765
+```
+
+In Edge, load `extension/edge-share` as an unpacked extension, open the extension popup, keep the
+relay URL as `http://127.0.0.1:8765` for local testing or set your hosted relay URL, then click
+`Share` and copy the link.
+
+Open the `browser-connection` control panel (`controlPanelUrl` from `browser_list`), paste the link
+into `Shared Link`, and add it as `edge`. The target appears as `kind=shared-extension`; selecting
+it makes MCP tools route through the extension session instead of a CDP port:
+
+```toml
+[mcp_servers.playwright]
+command = "browser-connection"
+args = [
+  "--project", "dg-my-project",
+  "--browser-share", "edge=https://relay.example/share/session#agent=token",
+  "--active-browser", "managed",
+]
+```
+
+The share link is a bearer credential. Anyone with the link can control that shared session until
+the user clicks `Stop` in the extension or the relay session is removed. Extension sharing supports
+common browser tools such as navigate, snapshot, evaluate, click, type, key press, and screenshot,
+but it is not full CDP/VNC parity and protected Edge pages may reject actions.
+
+## Personal browser
+
+You can attach an already running desktop Chrome/Chromium browser if it exposes a CDP port.
+When `browser-connection` runs inside Docker, use a host-reachable address such as
+`host.docker.internal`, not `127.0.0.1`.
+
+```bash
+google-chrome \
+  --remote-debugging-address=0.0.0.0 \
+  --remote-debugging-port=9222 \
+  --user-data-dir="$HOME/.browser-connection-personal" \
+  --no-first-run
+```
+
+To also view that desktop browser through noVNC, expose the host desktop/browser through VNC:
+
+```bash
+x11vnc -display :0 -rfbport 5900 -listen 0.0.0.0 -nopw -forever -shared
+```
+
+Then register both the CDP endpoint and the VNC display endpoint:
+
+```toml
+[mcp_servers.playwright]
+command = "browser-connection"
+args = [
+  "--project", "dg-my-project",
+  "--personal-browser", "http://host.docker.internal:9222",
+  "--personal-vnc", "host.docker.internal:5900",
+]
+```
+
+Multiple browser targets can be configured and switched at runtime. This example starts on the
+Docker-managed noVNC browser and keeps the personal browser ready in the noVNC control panel:
+
+```toml
+[mcp_servers.playwright]
+command = "browser-connection"
+args = [
+  "--project", "dg-my-project",
+  "--browser", "personal=http://host.docker.internal:9222",
+  "--browser-vnc", "personal=host.docker.internal:5900",
+  "--browser", "work=http://127.0.0.1:9333",
+  "--active-browser", "managed",
+]
+```
+
+Environment alternatives:
+
+```bash
+export BROWSER_CONNECTION_PERSONAL_CDP_ENDPOINT=http://host.docker.internal:9222
+export BROWSER_CONNECTION_PERSONAL_VNC_ENDPOINT=host.docker.internal:5900
+export BROWSER_CONNECTION_BROWSERS=work=http://127.0.0.1:9333
+export BROWSER_CONNECTION_BROWSER_VNCS=work=host.docker.internal:5901
+export BROWSER_CONNECTION_BROWSER_SHARES=edge=https://relay.example/share/session#agent=token
+export BROWSER_CONNECTION_ACTIVE_BROWSER=managed
+```
+
+`browser_list` reports each target's `cdpEndpoint`, `vncEndpoint`, `novncUrl`, and `shareUrl`. If a
+target has a VNC endpoint but no explicit noVNC URL, `browser_select` starts a lightweight noVNC
+proxy for that target unless `--no-start-browser` is set.
+
+Open the reported `controlPanelUrl` to choose `managed`, `personal`, or any configured browser from
+the noVNC UI. The same `browser-connection` process keeps running, and MCP browser tools use the new
+active target on the next tool call.
 
 ## Hermes MCP config
 
@@ -70,8 +181,16 @@ browser_click(selector)
 browser_type(selector, text)
 browser_press_key(key)
 browser_take_screenshot(full_page?)
+browser_list()
+browser_select(name, cdp_endpoint?, vnc_endpoint?, novnc_url?, share_url?)
 ```
 
+The noVNC control panel is the interactive switcher. Use `browser_select` with `name=managed` to
+return to the Rust-managed noVNC/CDP browser, or with
+`name=personal`, `cdp_endpoint=http://host.docker.internal:9222`, and
+`vnc_endpoint=host.docker.internal:5900` to connect a personal browser without restarting the MCP
+server.
+
 ## Smoke test
 
 ```bash

artifacts/README.md

@@ -0,0 +1,15 @@
+# Downloadable Artifacts
+
+## Edge share extension
+
+Download `edge-share-extension.tar.gz`, extract it, then open Edge:
+
+```text
+edge://extensions
+```
+
+Enable `Developer mode`, choose `Load unpacked`, and select the extracted
+`edge-share` folder.
+
+The extension connects to `browser-connection-relay` and produces share links
+that can be pasted into the `browser-connection` control panel.

changelog.d/20260624_071400_personal_browser_targets.md

@@ -0,0 +1,9 @@
+---
+bump: minor
+---
+
+### Added
+- Add named MCP browser targets so agents can connect to a personal CDP browser and switch between personal, external, and Rust-managed browser sessions at runtime.
+- Add optional VNC/noVNC display metadata for browser targets, including a Docker-managed noVNC proxy for host personal browsers.
+- Add a local noVNC control panel for choosing the active browser target while one `browser-connection` MCP process keeps running.
+- Add link-based shared browser targets through an Edge extension, `browser-connection-relay`, and `--browser-share NAME=URL`.

extension/edge-share/README.md

@@ -0,0 +1,102 @@
+# Browser Connection Edge Share
+
+Static Microsoft Edge extension skeleton for sharing a running Edge browser with
+`browser-connection` through a relay link. This directory intentionally has no
+build step and no dependencies.
+
+## Install for development
+
+1. Open `edge://extensions`.
+2. Enable `Developer mode`.
+3. Choose `Load unpacked`.
+4. Select this `extension/edge-share` directory.
+5. Open the extension popup, enter the relay URL, and click `Share`.
+
+The popup generates a one-time browser session and a share link such as:
+
+```text
+https://relay.example.com/share/<session_id>#agent=<agent_token>
+```
+
+The extension connects as the browser side to:
+
+```text
+wss://relay.example.com/ws/browser/<session_id>?token=<browser_token>&agent_token=<agent_token>
+```
+
+For local development, `http://127.0.0.1:8765` becomes
+`ws://127.0.0.1:8765/ws/browser/...`.
+
+## Relay protocol
+
+On WebSocket open the extension sends:
+
+```json
+{
+  "type": "hello",
+  "role": "browser",
+  "protocolVersion": 1,
+  "sessionId": "<session_id>",
+  "userAgent": "<navigator.userAgent>"
+}
+```
+
+The relay forwards command messages from the agent:
+
+```json
+{
+  "type": "command",
+  "id": "request-1",
+  "command": "navigate",
+  "params": {
+    "url": "https://example.com"
+  }
+}
+```
+
+The extension replies:
+
+```json
+{
+  "type": "response",
+  "id": "request-1",
+  "ok": true,
+  "result": {}
+}
+```
+
+Failed commands return `ok: false` and an `error` string.
+
+## Commands
+
+All commands accept optional `params.tabId`. If omitted, the extension uses the
+last selected tab or the active tab in the last focused window.
+
+- `navigate`: requires `url`; uses `chrome.tabs.update`.
+- `evaluate`: requires `expression`; runs JavaScript with `Runtime.evaluate`.
+- `snapshot`: returns title, URL, visible text, active element, and common
+  interactive elements.
+- `click`: requires `selector`; scrolls, dispatches mouse events, and calls
+  `click()`.
+- `type`: requires `text`; uses `selector` when provided, otherwise the active
+  element. Set `replace: true` to replace existing input text.
+- `press_key`: requires `key`; dispatches common keyboard events through CDP.
+- `screenshot`: returns a base64 PNG by default, or JPEG with
+  `format: "jpeg"`.
+- `list_tabs`: returns basic tab metadata.
+- `activate_tab`: activates `tabId` or the current target tab.
+
+## Notes and limits
+
+- This extension is the browser side for `browser-connection-relay` and the
+  `browser-connection` shared-extension driver.
+- `chrome.debugger` exposes useful CDP commands but is not identical to a full
+  remote debugging port.
+- Pages such as `edge://`, extension pages, store pages, and policy-restricted
+  tabs may reject debugger, scripting, or screenshot actions.
+- The share link should be treated as a bearer credential. Anyone with the link
+  can control the shared session until the user clicks `Stop` or the relay
+  expires the session.
+- The extension uses broad host permissions so it can connect to arbitrary relay
+  hosts during development. A production build should narrow this to known relay
+  origins.

extension/edge-share/manifest.json

@@ -0,0 +1,26 @@
+{
+  "manifest_version": 3,
+  "name": "Browser Connection Edge Share",
+  "version": "0.1.0",
+  "description": "Share this Edge browser with browser-connection through a relay link.",
+  "permissions": [
+    "activeTab",
+    "debugger",
+    "scripting",
+    "storage",
+    "tabs"
+  ],
+  "host_permissions": [
+    "<all_urls>"
+  ],
+  "background": {
+    "service_worker": "service_worker.js"
+  },
+  "action": {
+    "default_title": "Edge Share",
+    "default_popup": "popup.html"
+  },
+  "content_security_policy": {
+    "extension_pages": "script-src 'self'; object-src 'self'; connect-src 'self' http://* https://* ws://* wss://*;"
+  }
+}