claude-cook 1.11.3 → 1.11.4

package/agents/cook-pm.md

@@ -109,7 +109,9 @@ When running under `/cook:pm-start` and `pm-loop.sh`, you MUST avoid asking the
 
 ## PM Loop Launch is MANDATORY
 
-When spawned by `/cook:pm-start`, you MUST launch `pm-loop.sh --background` via Bash after executing the first cycle. The only exception is when `--manual` flag is explicitly set. Without the loop, the PM does one cycle and stops — defeating the purpose of autonomous operation. Do NOT wrap in `nohup` or append `&` — the `--background` flag handles detaching internally via `setsid`/`disown`. The script prints the PID and exits immediately.
+When spawned by `/cook:pm-start`, you MUST launch `pm-loop.sh` via the Bash tool with `run_in_background=true` after executing the first cycle. The only exception is when `--manual` flag is explicitly set. Without the loop, the PM does one cycle and stops — defeating the purpose of autonomous operation.
+
+**IMPORTANT:** Use the Bash tool with `run_in_background=true` — this runs in Claude Code's background compute so the user sees live progress in the UI. Do NOT use `--background` flag, `nohup`, `setsid`, `disown`, or `&`. Do NOT set `timeout` on the Bash tool — the loop runs indefinitely until milestone complete or `.pm-stop`. The loop runs in foreground mode within the background task, showing live progress bars and status updates.
 
 </philosophy>
 

package/commands/cook/pm-start.md

@@ -142,19 +142,22 @@ Follow the action for the detected state as defined in `pm-cycle.md`:
 
 **You MUST launch pm-loop.sh unless `--manual` flag is explicitly set.** This is not optional. The loop is what makes the PM autonomous — without it, the PM does one cycle and stops.
 
-**If `--manual` is NOT set**, run this command via Bash tool immediately after the first cycle completes:
+**If `--manual` is NOT set**, launch pm-loop.sh using the Bash tool with `run_in_background=true` immediately after the first cycle completes:
 
 ```bash
 ~/.claude/scripts/pm-loop.sh \
   --phase={X} \
   --interval={poll_interval} \
   --max-iterations={max_iterations} \
-  --background \
   ${init_flag} \
   ${prd_flag}
 ```
 
-**IMPORTANT:** Do NOT wrap this in `nohup` or append `&`. The `--background` flag makes `pm-loop.sh` handle its own detaching internally (via `setsid` or `nohup+disown`). The script prints the PID, writes the pid file, and exits immediately — the loop continues in a fully detached process.
+**IMPORTANT:**
+- Use the Bash tool with `run_in_background=true` — this runs in Claude Code's background compute so the user sees live progress in the UI.
+- Do NOT use `--background` flag, `nohup`, or `&`. Let Claude Code manage the background process.
+- Do NOT use `timeout` on the Bash tool — the loop runs indefinitely until milestone complete or `.pm-stop`.
+- The loop runs in foreground mode within the background task, showing live progress bars and status updates.
 
 Where:
 - `${init_flag}` is `--init` if the `--init` flag was provided
@@ -164,11 +167,11 @@ Where:
 After launching, confirm to user:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- PM ► LOOP STARTED
+ PM ► LOOP STARTED (background compute)
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-PM loop running in background (PID: {pid})
-Polling every {interval}s
+PM loop running in background compute.
+Polling every {interval}s. Progress visible in Claude Code UI.
 
 Stop with: /cook:pm-stop
 Status:    /cook:pm-status

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-cook",
-  "version": "1.11.3",
+  "version": "1.11.4",
   "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code, OpenCode and Gemini by TÂCHES.",
   "bin": {
     "claude-cook": "bin/install.js"