@grum-os/cli 0.3.34 → 0.3.36
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 +6 -2
- package/content.md5 +1 -1
- package/grum.mjs +296 -290
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -34,6 +34,10 @@ Then choose **check**. New drift is listed with a one-line fix, and Grum offers
|
|
|
34
34
|
|
|
35
35
|
Once you are signed in, the third row is **logout**. Run `grum` again and choose **setup** to change the link or turn Cursor off. Enter keeps each current setting.
|
|
36
36
|
|
|
37
|
+
## Rescan a workspace
|
|
38
|
+
|
|
39
|
+
After changing code, run `grum scan` in the linked repository to start a fresh server-side scan and follow its progress in the terminal. Add `--root <dir>` when the workspace is a folder inside a monorepo. The scan runs in Grum and may take a few minutes. Ctrl+C stops waiting, but the scan keeps running. Only workspace owners can start scans.
|
|
40
|
+
|
|
37
41
|
## Set up with your agent
|
|
38
42
|
|
|
39
43
|
A coding agent can do this setup. You paste one prompt into the chat and approve a code in the browser. You do not need to open a terminal.
|
|
@@ -41,7 +45,7 @@ A coding agent can do this setup. You paste one prompt into the chat and approve
|
|
|
41
45
|
The page you open is [app.grum.so/agent/human](https://app.grum.so/agent/human). The prompt there points the agent at [app.grum.so/agent](https://app.grum.so/agent), which is the instructions in markdown. The agent runs:
|
|
42
46
|
|
|
43
47
|
```sh
|
|
44
|
-
npx --yes @grum-os/cli setup --agent cursor --json
|
|
48
|
+
npx --yes --prefer-online @grum-os/cli@latest setup --agent cursor --json
|
|
45
49
|
```
|
|
46
50
|
|
|
47
51
|
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.
|
|
@@ -222,7 +226,7 @@ Store it as a secret. Do not commit it. The token acts as you, in every workspac
|
|
|
222
226
|
```yaml
|
|
223
227
|
# GitHub Actions
|
|
224
228
|
- name: Check the design contract
|
|
225
|
-
run: npx --yes @grum-os/cli check --ci
|
|
229
|
+
run: npx --yes --prefer-online @grum-os/cli@latest check --ci
|
|
226
230
|
env:
|
|
227
231
|
GRUM_TOKEN: ${{ secrets.GRUM_TOKEN }}
|
|
228
232
|
```
|
package/content.md5
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
|
|
1
|
+
6eae4c5cfe270234b5835ae3f8d1253b
|