@grum-os/cli 0.3.36 → 0.3.38
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/content.md5 +1 -1
- package/grum.mjs +152 -152
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -91,9 +91,9 @@ These are the files setup writes. They merge into what is already there, and a s
|
|
|
91
91
|
Codex keeps project configuration and hooks under your control. Grum will not appear in MCP or Hooks until you do both of these:
|
|
92
92
|
|
|
93
93
|
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`.
|
|
94
|
-
2. Open **Settings > Hooks
|
|
94
|
+
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.
|
|
95
95
|
|
|
96
|
-
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
|
|
96
|
+
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.
|
|
97
97
|
|
|
98
98
|
| File | What it does |
|
|
99
99
|
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
package/content.md5
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
|
|
1
|
+
3106fdfb601b20e9df95c8e127d60964
|