@grum-os/cli 0.3.14 → 0.3.16
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 +19 -17
- package/content.md5 +1 -1
- package/grum.mjs +224 -218
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -84,10 +84,10 @@ These are the files setup writes. They merge into what is already there, and a s
|
|
|
84
84
|
|
|
85
85
|
`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.
|
|
86
86
|
|
|
87
|
-
Codex keeps
|
|
87
|
+
Codex keeps project configuration and hooks under your control, so two things are yours after trusting the folder:
|
|
88
88
|
|
|
89
|
-
1.
|
|
90
|
-
2. Open
|
|
89
|
+
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.
|
|
90
|
+
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`.
|
|
91
91
|
|
|
92
92
|
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.
|
|
93
93
|
|
|
@@ -159,7 +159,9 @@ grum request "color:raw:#3C3C3C" \
|
|
|
159
159
|
--url http://localhost:3000
|
|
160
160
|
```
|
|
161
161
|
|
|
162
|
-
|
|
162
|
+
Captures default to the local app. Use `grum request <key> [<key>...] --live` to capture the configured live site after a release. Grum uses the route identified by the finding's source file when it can, otherwise the site's configured URL. This leaves the saved local-app URL unchanged and adds no confirmation prompt. The target URL is printed before capture.
|
|
163
|
+
|
|
164
|
+
`--url` is the page where the element renders, or an HTML file in the repo (`./index.html`) when there is no dev server. An explicit `--url` takes priority over `--live`, including when a shared component needs a specific page. A page behind a login is captured through the Grum Chrome extension, in your own browser session. `--browser chrome` or `--browser safari` picks the browser. `--no-capture` sends the request with no picture.
|
|
163
165
|
|
|
164
166
|
```sh
|
|
165
167
|
grum capture reset
|
|
@@ -231,19 +233,19 @@ Store it as a secret. Do not commit it. The token acts as you, in every workspac
|
|
|
231
233
|
|
|
232
234
|
The menu covers check, setup, and sign-in. These are the same actions as flags, for scripts and CI.
|
|
233
235
|
|
|
234
|
-
| Command
|
|
235
|
-
|
|
|
236
|
-
| `grum`
|
|
237
|
-
| `grum login` / `grum logout`
|
|
238
|
-
| `grum setup [--root <dir>]`
|
|
239
|
-
| `grum check [flags]`
|
|
240
|
-
| `grum request <key> [<key>...] [--reason "..."] [--url <page>] [--browser chrome | safari] [--no-capture]` | Ask the owners to allow drift items; items on one page capture together. |
|
|
241
|
-
| `grum uninstall [--yes]`
|
|
242
|
-
| `grum capture reset`
|
|
243
|
-
| `grum contract`
|
|
244
|
-
| `grum init cursor [--remove] [--force] [--local-only] [--pre-commit]`
|
|
245
|
-
| `grum init codex [--remove] [--force] [--local-only] [--pre-commit]`
|
|
246
|
-
| `grum init claude [--remove] [--force] [--local-only] [--pre-commit]`
|
|
236
|
+
| Command | What it does |
|
|
237
|
+
| ----------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
|
|
238
|
+
| `grum` | The menu. Check, setup (including Cursor), or sign in. |
|
|
239
|
+
| `grum login` / `grum logout` | Sign this computer in to Grum, or out. |
|
|
240
|
+
| `grum setup [--root <dir>]` | Sign in, link this repository, and ask about Cursor and the pre-commit check. |
|
|
241
|
+
| `grum check [flags]` | Check the working tree. See the flags below. |
|
|
242
|
+
| `grum request <key> [<key>...] [--reason "..."] [--url <page>] [--live] [--browser chrome | safari] [--no-capture]` | Ask the owners to allow drift items; items on one page capture together. |
|
|
243
|
+
| `grum uninstall [--yes]` | Remove Grum from this repository and this computer. See [Uninstall](#uninstall). |
|
|
244
|
+
| `grum capture reset` | Clear this repository's saved capture-browser sign-ins. |
|
|
245
|
+
| `grum contract` | Print the contract packet. |
|
|
246
|
+
| `grum init cursor [--remove] [--force] [--local-only] [--pre-commit]` | Write or remove the Cursor files without the menu. `--pre-commit` adds the commit check. `--no-pre-commit` removes it. |
|
|
247
|
+
| `grum init codex [--remove] [--force] [--local-only] [--pre-commit]` | The same for Codex: `.codex/config.toml`, `.codex/hooks.json` and the `AGENTS.md` block. |
|
|
248
|
+
| `grum init claude [--remove] [--force] [--local-only] [--pre-commit]` | The same for Claude Code: `.mcp.json`, `.claude/settings.json` and the `CLAUDE.md` block. |
|
|
247
249
|
|
|
248
250
|
```sh
|
|
249
251
|
grum check --staged # drift in the blocks staged for commit
|
package/content.md5
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
|
|
1
|
+
84f2169046dc8c8791cbbdd0dd0ee7f0
|