Scheduled tasks: no way to set reasoning effort or permission mode after creation (GUI or MCP)#22770

Before submitting

• I searched existing issues and did not find a duplicate.

Problem

A scheduled task's reasoning effort and permission (runtime) mode can't be changed after creation, from either the GUI or MCP.

• The scheduled-task editor in the web/desktop GUI has no effort or permission control. PR #16592 ("choose reasoning, speed, and permissions for scheduled tasks") proposed one but was closed unmerged.
• update_scheduled_task has no field for either. Calling it from a thread whose mode is lower than the task's (e.g. an auto thread editing a full-access task) is refused with runtime_mode_escalation_denied, even for a prompt-only change.
• The only way to change a task's mode is to recreate it with schedule_task from a thread already in the target mode. That copies the calling thread's model options, so per-task options are lost (#16833), and the workspace resets to a worktree from origin/main (#19786).

Steps to reproduce

1. Create a scheduled task from a full-access thread, with model option effort: medium and workspace set to the project checkout.
2. Try to move it to auto: there is no GUI control, and update_scheduled_task has no field.
3. From an auto thread, recreate it with schedule_task. scheduled_tasks now shows runtime_mode = auto, but model_selection_json has no effort option and workspace_strategy_json is {"type":"worktree","baseRef":"main","startFromOrigin":true}.
4. The workspace can be fixed in the GUI; effort cannot.

Expected

The scheduled-task editor exposes reasoning effort and permission mode, or the MCP tools accept them, still subject to the escalation check.

Environment

T3 Code (Beta) 0.1.0, macOS, Claude provider.

Related: #16833, #19786, #16592.