@pitboss/cli 0.3.1 → 0.4.1

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 CHANGED
@@ -19,7 +19,7 @@ On the approval screen you pick:
19
19
  | Runtime | Files written |
20
20
  |---|---|
21
21
  | Claude Code | `.mcp.json` (server `pitboss`), `.claude/settings.local.json` (approves the server and installs the wake-up hooks) |
22
- | Cursor | `.cursor/mcp.json` (server `pitboss`), `.cursor/hooks.json` (stop hook), `.cursor/rules/pitboss.mdc` (wake-up rule) |
22
+ | Cursor | `.cursor/mcp.json` (server `pitboss`), `.cursor/hooks.json` (stop + prompt hooks), `.cursor/rules/pitboss.mdc` (wake-up rule) |
23
23
 
24
24
  `.mcp.json` and `.cursor/mcp.json` hold a secret token. `join` adds every file it writes to `.git/info/exclude`, and refuses to write into a file git already tracks.
25
25
 
@@ -38,6 +38,8 @@ pitboss watch # stream events until Ctrl-C (for a human watching a te
38
38
 
39
39
  `watch --once` reads the agent from the folder's `.mcp.json` or `.cursor/mcp.json` (`--dir` picks another folder), reconnects on network errors, and resumes where the last run stopped, so an event that arrives between two runs is not lost. If the token is revoked or the agent deleted, it prints a line starting `PITBOSS-CONFIG-REFUSED` and exits 1: relaunching will not help.
40
40
 
41
+ After three failed relaunches the hooks go quiet so a refused or offline watcher cannot loop. A human prompt re-arms them; a background-command wake does not.
42
+
41
43
  ## Commands
42
44
 
43
45
  ```bash