@grum-os/cli 0.3.40 → 0.3.43

package/README.md

@@ -1,4 +1,4 @@
-<img src="https://cdn.jsdelivr.net/npm/@grum-os/cli/brand.png" alt="Grum" width="228" height="64" />
+<img src="https://cdn.jsdelivr.net/npm/@grum-os/cli/brand.png" alt="Grum" width="224" height="59" />
 
 # Grum
 
@@ -54,6 +54,8 @@ Rerunning setup refreshes existing integration files while preserving your own h
 
 Agent setup asks where your app runs locally. Repository URLs and `index.html` are suggestions; the agent must ask before selecting one. An older saved address is confirmed once. A local HTTP page must return 200; redirects, 404, access denial, connection refusal and timeouts keep setup incomplete. After a successful probe, the agent opens the page in its visible browser (Codex uses its browser panel), checks rendering, and reports any problems. Setup returns `preview-local-app` until the agent acknowledges the shown URL with `localPreviewed` in `grum_setup`, or `--local-previewed <url>` in the CLI. If browser control is unavailable, the agent asks you to open the URL and confirm it renders. A new address requires a new preview. An explicitly chosen static HTML file also needs preview; file existence does not prove rendering. Choose `none` only if you want to skip the local app.
 
+Agents may also open a page in their visible browser when they want you to see the page they are referring to or asking you about. Grum setup operations still use the CLI; when browser control is available, the agent opens the page itself.
+
 The menu and the commands above stay as they are. `--agent` is an extra way in, not a replacement.
 
 ## Cursor

package/content.md5

@@ -1 +1 @@
-62a2e64d1373e651dc499fce541a5d89
+2732aab4724ecf82f3141d7e67d829f1