@grum-os/cli 0.3.37 → 0.3.39

package/README.md

@@ -50,6 +50,10 @@ npx --yes --prefer-online @grum-os/cli@latest setup --agent cursor --json
 
 Use `codex`, `claude` (Claude Code) or `generic` instead of `cursor` for those agents. The command prints JSON. Exit 0 means ready, exit 2 means the agent should take the next action and run it again, and exit 1 is a fault. `grum doctor --agent cursor --json` reports the same checks and changes nothing.
 
+Rerunning setup refreshes existing integration files while preserving your own hooks and settings. The agent finishes verification with `grum_doctor` through MCP, which confirms the connection in that chat. If a shell check cannot verify the tools, it asks the agent to discover and call the tool before sending you to settings. Codex is ready when its MCP connection is confirmed and a hook has successfully run. Changed hook commands require review in Codex; new Grum releases using the same commands keep their existing trust.
+
+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.
+
 The menu and the commands above stay as they are. `--agent` is an extra way in, not a replacement.
 
 ## Cursor
@@ -91,9 +95,9 @@ These are the files setup writes. They merge into what is already there, and a s
 Codex keeps project configuration and hooks under your control. Grum will not appear in MCP or Hooks until you do both of these:
 
 1. Trust this folder when Codex asks. Then in **Settings > MCP servers**, turn on **grum**. If Codex labels the server with this folder's name, pick the one whose command runs `grum.mjs`.
-2. Open **Settings > Hooks**, open this project, and allow Grum's 3 commands (they say "need review" and run `grum.mjs hook ...`). This is a different screen from MCP. In the terminal app, run `/hooks`.
+2. Open **Settings > Hooks** for this project and check Grum's 3 commands (they say "need review" and run `grum.mjs hook ...`). Turn on any that are off; this is separate from MCP. In the terminal app, run `/hooks` to review the list.
 
-Without step 2 the tools still work and the agent still follows the guidance, but nothing checks when Codex stops and `git commit` and `git push` are not refused. Until a hook has run, the agent reminds you.
+Without step 2 the tools still work and the agent still follows the guidance, but nothing checks when Codex stops and `git commit` and `git push` are not refused. Until Grum observes a successful hook run, it reports that hook status is unconfirmed.
 
 | File                 | What it does                                                                                                                                            |
 | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |

package/content.md5

@@ -1 +1 @@
-203fce46ed443a50632cb1fa157b387c
+f02d8c8020ae408b614eacde9aab16bb