@vibebrowser/mcp 0.2.5 → 0.2.6

package/README.md

@@ -279,6 +279,7 @@ For the full walkthrough, see `docs/openclaw-local-browser.md`.
 `vibebrowser-cli` mirrors the OpenClaw browser CLI shape for the real local-browser path:
 
 ```bash
+npx -y --package @vibebrowser/mcp vibebrowser-cli sessions
 npx -y --package @vibebrowser/mcp vibebrowser-cli --remote <extension-uuid> status
 npx -y --package @vibebrowser/mcp vibebrowser-cli --remote <extension-uuid> tabs
 npx -y --package @vibebrowser/mcp vibebrowser-cli --remote <extension-uuid> open https://example.com
@@ -294,6 +295,52 @@ The package now exposes two executables:
 
 `vibebrowser-cli` accepts the OpenClaw-style `--browser-profile` flag for compatibility and supports `--json` for machine-readable output. Unlike OpenClaw's managed `openclaw` browser profile, this CLI always targets the real Vibe-connected browser session.
 
+Local-session selection:
+
+- `vibebrowser-cli sessions` lists connected local browser sessions.
+- `vibebrowser-cli --session <id> ...` targets a specific local session.
+- If `--session` is omitted in local mode, the CLI uses the first connected session.
+- In remote mode, `--remote <extension-uuid>` remains the explicit browser selector.
+
+Snapshot behavior is tool-only (no legacy snapshot RPC shortcut):
+
+- `snapshot` (default) resolves via `take_md_snapshot`
+- `snapshot --format aria` resolves via `take_a11y_snapshot`
+
+This keeps CLI behavior aligned with extension-supported tools and ensures page targeting works consistently with `--page-id`/`--pageId`.
+
+For navigation-style operations, responses now include page content when page state changes:
+
+- CLI `open` / `navigate` include `pageContent` in JSON output.
+- MCP tool calls for navigation-style tools return text content that includes current page state (with snapshot fallback when needed).
+
+### OpenClaw Integration
+
+There are two ways to use Vibe with OpenClaw:
+
+**Option A: Cloud OpenClaw controlling local browser**
+
+If OpenClaw runs in the cloud but you want it to control your local browser:
+
+1. Install the Vibe extension and enable **Remote** mode (see [docs/openclaw-local-browser.md](docs/openclaw-local-browser.md))
+2. Start the local HTTP bridge: `vibebrowser-mcp openclaw --remote <extension-uuid>`
+3. Register the MCP URL in OpenClaw
+
+**Option B: OpenClaw skill for local agents**
+
+For OpenClaw agents that need your real browser context (logged-in sessions, existing tabs):
+
+1. Copy the Vibe skill from this package to your OpenClaw skills folder
+2. Set `VIBE_EXTENSION_UUID` environment variable
+3. Use `vibebrowser-cli` commands in your agent prompts
+
+The skill is located at [`openclaw/vibebrowser/SKILL.md`](openclaw/vibebrowser/SKILL.md) and provides:
+- Full OpenClaw-compatible CLI commands (`status`, `tabs`, `snapshot`, `click`, `type`, etc.)
+- `--json` output for machine parsing
+- Environment-based configuration
+
+See [docs/openclaw-local-browser.md](docs/openclaw-local-browser.md) for the complete walkthrough.
+
 ## Local LLM: `serve` Command
 
 Run a local LLM with one command — no cloud API keys required. Automatically installs [Ollama](https://ollama.com), downloads the model, and starts serving an OpenAI-compatible API.

package/dist/browser-cli.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"browser-cli.d.ts","sourceRoot":"","sources":["../src/browser-cli.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAsEpC,wBAAgB,sBAAsB,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,CAK7D;AAED,wBAAgB,4BAA4B,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,CAGnE"}
+{"version":3,"file":"browser-cli.d.ts","sourceRoot":"","sources":["../src/browser-cli.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AA+EpC,wBAAgB,sBAAsB,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,CAK7D;AAED,wBAAgB,4BAA4B,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,CAGnE"}