@viraatdas/rudder 1.0.34 → 1.0.35

package/README.md

@@ -388,6 +388,7 @@ through suggestions and `Enter` to choose one.
 | `/model` | Open the provider-first model picker: choose Claude or Codex, then model, then effort when supported |
 | `/plan` | Toggle Rudder's read-only plan mode for task pane submissions |
 | `/plan <task>` | Start one read-only planning session without toggling plan mode |
+| `/rudder-plan <task>` | Start a planning coordinator that decomposes the task and spawns worker agents |
 | `/run <task>` | Start an implementation run even when plan mode is on |
 | `/login` | Open browser login for Rudder Cloud |
 | `/cloud` | Ask whether to onload the current Rudder workspace or start a fresh Fly worker |
@@ -473,6 +474,12 @@ the backend's native planning/read-only controls:
   and `--search`, so filesystem writes are blocked and the native Responses
   `web_search` tool is available.
 - Claude planners launch with Claude Code's native `--permission-mode plan`.
+
+`/rudder-plan <task>` uses the same read-only planner controls, but asks the
+planner to emit a structured `RUDDER_PLAN_TASKS` block. When Rudder sees that
+block, it starts each listed task as a normal isolated worktree agent. If the
+planner asks follow-up questions instead of emitting the block, Rudder does not
+spawn workers.
 - Rudder only prefixes the task with a short planning request; it no longer
   injects a custom planner contract.
 - Normal implementation runs are unchanged: they still create worktrees and use

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@viraatdas/rudder",
-  "version": "1.0.34",
+  "version": "1.0.35",
   "description": "A Claude Code-style terminal app for running coding agents with worktree-isolated runs.",
   "homepage": "https://rudder.viraat.dev",
   "type": "module",