Skip to content

fix: forward task configuration through stdin-prompt-stream#11778

Merged
cte merged 2 commits intomainfrom
fix/forward-configuration-in-stdin-stream
Feb 27, 2026
Merged

fix: forward task configuration through stdin-prompt-stream#11778
cte merged 2 commits intomainfrom
fix/forward-configuration-in-stdin-stream

Conversation

@daniel-lxs
Copy link
Member

@daniel-lxs daniel-lxs commented Feb 27, 2026

Summary

  • The stdin-prompt-stream start command only accepted prompt — any configuration from the worker's StartNewTask was silently dropped
  • Custom modes (e.g. ask-artifacts), disabled tools, and other task-level settings never reached the extension
  • The fix adds configuration support to the protocol and registers custom modes via updateCustomMode() so they survive the CustomModesManager's merge cycle

Changes (5 files, +30/-8 lines)

  • packages/types/src/vscode-extension-host.ts: Add taskConfiguration field to WebviewMessage
  • apps/cli/src/commands/cli/stdin-stream.ts: Parse optional configuration from start command
  • apps/cli/src/agent/extension-host.ts: Accept and forward configuration in runTask()
  • src/core/webview/webviewMessageHandler.ts: Pass taskConfiguration to createTask()
  • src/core/webview/ClineProvider.ts: Register custom modes via updateCustomMode() in createTask()

Backward-compatible: older CLIs ignore the extra JSON field; workers that don't send configuration trigger no behavior change.

Test plan

  • All 5305 tests pass (365 test files)
  • Type check and lint pass
  • E2E verified with companion Roomote2 PR

Companion PR: https://github.com/RooCodeInc/Roomote/pull/177

🤖 Generated with Claude Code

Interactively review PR in Roo Code Cloud

@dosubot dosubot bot added size:S This PR changes 10-29 lines, ignoring generated files. bug Something isn't working labels Feb 27, 2026
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>
@daniel-lxs daniel-lxs force-pushed the fix/forward-configuration-in-stdin-stream branch from 37a746c to 01783ed Compare February 27, 2026 05:19
@dosubot dosubot bot added size:M This PR changes 30-99 lines, ignoring generated files. and removed size:S This PR changes 10-29 lines, ignoring generated files. labels Feb 27, 2026
@cte cte merged commit a7c8275 into main Feb 27, 2026
7 checks passed
@github-project-automation github-project-automation bot moved this from New to Done in Roo Code Roadmap Feb 27, 2026
@cte cte deleted the fix/forward-configuration-in-stdin-stream branch February 27, 2026 05:41
@daniel-lxs
Copy link
Member Author

@mrubens these are the PRs that fix the problem with settings and custom modes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working size:M This PR changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants