open-browser-setup 1.0.0 → 1.0.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "open-browser-setup",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "Interactive installer for Open Browser — MCP server, CLI tool, skill, and Chrome extension setup",
   "type": "module",
   "bin": {

package/skill/{SKILL.md → open-browser/SKILL.md}

@@ -20,7 +20,7 @@ argument-hint: "describe what you want to do in the browser"
 
 # Open Browser
 
-Control the user's real Chrome browser via the `open-browser` CLI. Every command runs as a shell call and exits — the browser state persists through the Chrome extension between commands.
+Control the user's real Chrome browser via the `open-browser` CLI. A background daemon keeps the Chrome extension connected between commands.
 
 ## Prerequisites
 
@@ -33,14 +33,26 @@ Control the user's real Chrome browser via the `open-browser` CLI. Every command
 Every browser session follows this pattern:
 
 ```
-1. open-browser session          ← required first step, creates tab group + CDP
+1. open-browser start            ← starts daemon, connects extension, creates session + tab group
 2. open-browser navigate <url>   ← go to a page
 3. open-browser snapshot --json  ← see interactive elements with @eN refs
 4. open-browser click @e5        ← interact using refs from snapshot
 5. open-browser verify text "…"  ← confirm the result
 ```
 
-Always start with `session`. Always use `snapshot --json` to discover elements before interacting. The `@eN` refs (like `@e1`, `@e5`, `@e12`) are how you target elements for click, type, select, and other interactions.
+`open-browser start` handles everything — daemon, extension connection, session creation, and opens `localhost:9876` in the tab group. All subsequent commands are instant. If the daemon is already running, `start` is a no-op.
+
+The daemon also auto-starts when you run any command directly (e.g. `open-browser navigate`), but using `start` first is more reliable.
+
+Always use `snapshot --json` to discover elements before interacting. The `@eN` refs (like `@e1`, `@e5`, `@e12`) are how you target elements for click, type, select, and other interactions.
+
+## Daemon Commands
+
+```bash
+open-browser start              # Start daemon + session + tab group (all-in-one)
+open-browser stop               # Stop the daemon
+open-browser status             # Check if daemon is running
+```
 
 ## Using --json