ghostex-embedded-browser-use

# ghostex-embedded-browser-use Use Ghostex's CEF DevTools bridge for pages rendered inside Ghostex. This route does not require a second browser automation runtime. Enter through the `ghostex` CLI, not a configured MCP integration. Do not add a persistent `mcp_servers.ghostex-browser` entry. The temporary stdio bridge speaks MCP internally because that is the embedded page-control protocol, but launch it only through `ghostex browser mcp` for the current task. ## Requirements - Ghostex must be running before the CLI-launched bridge can attach to CEF. - A pane can be created or reused with `ghostex browser open <url>`. - The Ghostex CLI is bundled with the desktop app and linked on app startup. - Install this skill with `ghostex browser install-skill` when needed. ## CLI transport Launch the bridge directly from the CLI for the current task: ```bash ghostex browser mcp ``` The bridge reaches Ghostex's pages through the local gxserver with its token, so it needs no DevTools port. When that Ghostex's window is closed, the bridge says so instead of attaching to another Ghostex. Ghostex keeps its CEF remote-debugging port closed unless Settings > Debugging > Show debug UI controls was on when it started, or a port variable names one. Only for an app started that way, or an older Ghostex whose bridge still needs the port, pass it explicitly: ```bash ghostex browser mcp --port 9334 ``` The same value can be provided as `GHOSTEX_CEF_REMOTE_DEBUGGING_PORT`. ## Canonical loop 1. Open or reuse a suitable pane with `ghostex browser open <url>`. 2. Call `ghostex_list_pages` and select the intended pane with `ghostex_select_page` when multiple pages exist. 3. Read `ghostex_console_logs` before and after interactions when debugging. 4. Call `ghostex_snapshot` and choose stable `@e` element refs. 5. Perform one action with `ghostex_click`, `ghostex_fill`, `ghostex_press_key`, or `ghostex_navigate`. 6. Re-run `ghostex_snapshot` after navigation or a major DOM change. Verify the expected page state before continuing. 7. Use `ghostex_evaluate` for focused inspection and `ghostex_screenshot` when visual evidence matters. ## Opening panes - `ghostex browser open <url>` defaults to the agent process cwd as the project path and reuses a same-origin pane in that project. - Pass `--project-path "$PWD"` or `--project-id <id>` when the task belongs to a specific Ghostex project or worktree. - Keep the returned browser session id and the MCP page id from `ghostex_list_pages`; reuse them instead of opening duplicate panes. - Without a `pageId`, the tools drive your own page: the one you selected or used last, else the one you last opened with `ghostex browser open`, else the page in front of your project's Browser. They never pick another project's page on their own, and the user switching tabs does not move you; with no page of your own they return an error that says so. `ghostex_list_pages` lists your project's pages and marks the one you opened `agentPage`. - Use `--reuse exact` for exact-URL reuse, or `--new` only when a separate pane is intentional. ## Boundaries - Element refs are valid only for the current page state. Snapshot again after navigation or significant DOM changes. - Console collection starts when the CLI-launched bridge attaches, so attach before reproducing an error when possible. - Use `$ghostex-browser-use` for external Chrome, Chromium, Edge, or supported Electron page content through Cua Driver. - Use `$ghostex-computer-use` for native macOS UI outside the embedded page.