@viraatdas/rudder 1.1.19 → 1.1.20
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 +8 -13
- package/dist/native/rudder-native +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -148,11 +148,6 @@ with `Enter`.
|
|
|
148
148
|
| --- | --- |
|
|
149
149
|
| `/model` | Pick provider, then model, then effort |
|
|
150
150
|
| `/main` or `/m` | Start a new main-branch agent |
|
|
151
|
-
| `/plan` | Toggle read-only plan mode |
|
|
152
|
-
| `/plan <task>` | Run one read-only planning session |
|
|
153
|
-
| `/rudder-plan <task>` | Plan, then spawn worker agents for the steps |
|
|
154
|
-
| `/run <task>` | Start an implementation run even when plan mode is on |
|
|
155
|
-
| `/sync` | Rebase the selected worktree onto its base branch |
|
|
156
151
|
| `/review-all` | Combine completed worktrees and start a Codex review-all agent |
|
|
157
152
|
| `/merge-all` | Merge all completed worktrees |
|
|
158
153
|
| `/login` | Browser login for Rudder Cloud |
|
|
@@ -171,14 +166,15 @@ Your last provider, model, and effort are saved in `~/.rudder/config.json` and
|
|
|
171
166
|
reused next time. Rudder refreshes model metadata from
|
|
172
167
|
`https://models.dev/api.json` and falls back to local caches when offline.
|
|
173
168
|
|
|
174
|
-
##
|
|
169
|
+
## Planning (the default)
|
|
175
170
|
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
|
|
181
|
-
|
|
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.
|
|
182
178
|
|
|
183
179
|
## Worktrees and merging
|
|
184
180
|
|
|
@@ -189,7 +185,6 @@ the next time you open Rudder in that repo.
|
|
|
189
185
|
|
|
190
186
|
- Press `m` to merge the selected completed agent back into its branch.
|
|
191
187
|
- Press `M` to merge all completed agents. Rudder confirms first.
|
|
192
|
-
- Press `u` (or run `/sync`) to only rebase a worktree onto its base.
|
|
193
188
|
|
|
194
189
|
Clean merges become merge commits. If git reports conflicts, Rudder leaves the
|
|
195
190
|
conflicted state in place and can open an agent in the main checkout to help
|
|
Binary file
|
package/package.json
CHANGED