mirror of
https://github.com/RooVetGit/Roo-Code.git
synced 2026-08-28 05:27:24 +00:00
a7c8275e85
fix: forward task configuration through stdin-prompt-stream protocol The stdin-prompt-stream `start` command only accepted `prompt` — any `configuration` passed via the cloud worker's StartNewTask was silently dropped. This meant custom modes (e.g. `ask-artifacts`), disabled tools, and other task-level settings never reached the extension when running via the CLI harness. Changes: - Add optional `configuration` field to the `start` stdin command - Parse and forward it in `runStdinStreamMode` - Thread it through `ExtensionHost.runTask` → `newTask` webview message → `ClineProvider.createTask` (which already calls `setValues`) - Add `taskConfiguration` field to `WebviewMessage` type Backward-compatible: older CLIs ignore the extra field; older workers that don't send `configuration` trigger no change in behavior. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: cte <cestreich@gmail.com> |
||
|---|---|---|
| .. | ||
| build | ||
| cloud | ||
| config-eslint | ||
| config-typescript | ||
| core | ||
| evals | ||
| ipc | ||
| telemetry | ||
| types | ||
| vscode-shim | ||