@grum-os/cli 0.3.21 → 0.3.23

package/README.md

@@ -84,10 +84,10 @@ These are the files setup writes. They merge into what is already there, and a s
 
 `grum init codex` (or `grum setup`, when the repository has a `.codex` folder) puts the same contract inside Codex: the CLI, the desktop app and the IDE extension, on this computer. The agent reads the contract before it writes UI, checks before it finishes, and asks you once when nothing in the contract fits, exactly as Cursor's does.
 
-Codex keeps project configuration and hooks under your control, so two things are yours after trusting the folder:
+Codex keeps project configuration and hooks under your control. Grum will not appear in MCP or Hooks until you do both of these:
 
-1. In **Settings > MCP servers > Connected**, enable the entry named for the repository you are setting up. It may say `skillbase`, not Grum; it is the entry configured to run `grum.mjs`. Do not enable an unrelated integration.
-2. Open **Settings > Hooks**, open the project, and allow Grum's 3 hook commands (they show as "need review" and run `grum.mjs hook ...`). This is separate from the MCP connection. In the terminal app, run `/hooks`.
+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`.
 
 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.
 

package/content.md5

@@ -1 +1 @@
-04f75b22850b12871c55e53e6ea0fa0c
+7d0d2a052de41c2a457817597d216aaf