@grum-os/cli 0.3.12 → 0.3.13

package/README.md

@@ -34,6 +34,20 @@ Then choose **check**. New drift is listed with a one-line fix, and Grum offers
 
 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.
 
+## Set up with your agent
+
+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.
+
+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:
+
+```sh
+npx --yes @grum-os/cli setup --agent cursor --json
+```
+
+Use `codex` 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.
+
+The menu and the commands above stay as they are. `--agent` is an extra way in, not a replacement.
+
 ## Cursor
 
 Accepting Cursor in the menu puts Grum inside the agent. The agent follows the same contract a person sees in Grum, and it can ask the owners to allow something the contract does not have.

package/content.md5

@@ -1 +1 @@
-91072ef44363e75d825b32a6e9dedb31
+7dd72edbaa90ccb6621c5df3d474f9e8