Scheduled task editor: “Runs on” cannot change the task's machine #30112

Problem

When editing an existing scheduled task, the Runs on field looks like a machine dropdown (including a chevron), but cannot be clicked to select another machine. The user wants to move an existing scheduled task from one machine to another through this control, without manually recreating it.

This reports the current UI behavior and requests cross-machine task migration; it does not assume that the underlying migration capability already exists.

Steps to reproduce

1. Open Settings → Scheduled tasks.
2. Edit an existing task.
3. Try to open the Runs on machine selector and choose another linked machine.

Actual behavior

The machine selector is not clickable, so the task cannot be moved through the editor.

In the user's screenshot, the Edit task dialog shows Runs on: OldBatLaptop, with a dropdown chevron. The task has No project, uses Use the project checkout, runs every 300 minutes, and is enabled. It is also bound to an existing destination conversation (the editor says each run continues that conversation in its workspace with its current model).

Expected behavior

The Runs on dropdown should allow choosing another eligible linked machine and saving a move of the existing task.

Suggested acceptance criteria:

• Offer eligible destination machines and explain why an unavailable destination cannot be selected.
• Preserve the task's prompt, schedule, and enabled state when moving it.
• After a successful move, future scheduled runs execute on the destination and stop being scheduled on the source; avoid leaving two enabled copies.
• Validate destination project/workspace and provider requirements before committing the move. If the move fails, keep the source task intact and report the failure.
• Handle conversation-bound tasks explicitly: let the user resolve the destination conversation/binding, or explain the required action. Do not silently retain an unusable source-machine thread reference.

Evidence and environment

Reported by the user from the scheduled-task editor on 2026-11-03, with a screenshot supplied in the reporting conversation. The screenshot confirms the dialog contents and dropdown appearance; non-clickability is the user's observation. I have not independently reproduced the interaction. Exact application version and OS were not provided. The screenshot is not hosted publicly and is not attached here.

Related

• [Feature]: Load-balance scheduled task runs and delegated tasks, and cap how many run at once #27528 requests load balancing of scheduled runs between machines. This request is specifically about explicitly moving an existing task's owning/execution machine through the editor.
• fix(web): create tasks on a permitted connected environment #23244 fixes choosing a permitted environment when creating a task.
• feat(server): agents use linked environments through any T3 tool #16684 adds linked-environment MCP operations, including scheduled tasks, but does not describe migrating an existing task.

Filed on the user's behalf by Codex (GPT-6.1 Sol) through T3 Code.