@viraatdas/rudder 1.3.3 → 1.4.0

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
@@ -168,16 +168,19 @@ reused next time. Rudder refreshes model metadata from
168
168
 
169
169
  ## Planning (the default)
170
170
 
171
- Just type a task. The orchestrator decomposes it into a DAG of worker tasks and
172
- shows it for approval. While the plan awaits approval you can **discuss and refine
173
- it**: type changes into the task pane and the orchestrator re-plans and updates the
174
- DAG tree. The pane also shows the planner's assumptions/notes. Press `Enter` with an
175
- empty input to approve and launch; the scheduler then drains the DAG (todo
176
- in-progress review done) as dependencies merge. After launch, typing a new task
177
- folds it into the running DAG as a new node. When a worker finishes, Rudder reads back
178
- what it did and what work it found remaining (and reconstructs that from the diff if the
179
- agent did not say), so the plan keeps growing on its own. Type a sweeping change
180
- (\"rewrite this in Rust instead\") and the plan re-plans around the work already done.
171
+ Just type a task. Rudder opens the model's **interactive plan mode** right in the pane
172
+ (Claude's plan mode or Codex's `/plan`): the model researches your repo read-only and
173
+ proposes a plan you discuss and refine in-pane, exactly like using the agent's own plan
174
+ mode. It will not implement anything. When you are happy with the plan, press **`Ctrl+W`
175
+ then `a`** to approve: Rudder captures the plan, decomposes it into a DAG of worker tasks,
176
+ and shows you that DAG for one more approval. Press `Enter` to launch; the scheduler then
177
+ drains the DAG (todo in-progress review done) as dependencies merge.
178
+
179
+ After launch, typing a new task folds it into the running DAG as a new node. When a
180
+ worker finishes, Rudder reads back what it did and what work it found remaining (and
181
+ reconstructs that from the diff if the agent did not say), so the plan keeps growing on
182
+ its own. Type a sweeping change (\"rewrite this in Rust instead\") and the plan re-plans
183
+ around the work already done.
181
184
 
182
185
  ## Worktrees and merging
183
186
 
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@viraatdas/rudder",
3
- "version": "1.3.3",
3
+ "version": "1.4.0",
4
4
  "description": "A Claude Code-style terminal app for running coding agents with worktree-isolated runs.",
5
5
  "license": "MIT",
6
6
  "homepage": "https://rudder.viraat.dev",