Scheduled tasks (routines): show and allow choosing the model per routine
Open 💬 4 comments Opened Jul 1, 2026 by RubenARNAUD
Type: Feature request
Area: Scheduled tasks (routines) in the Claude desktop app / Claude Code (scheduled-tasks MCP server).
Problem
There's currently no way to see or set the model a scheduled task (routine) uses:
list_scheduled_tasks(MCP) returns schedule, cron,enabled,lastRunAt… but nomodelfield.update_scheduled_task(MCP) has nomodelparameter → the model can't be changed via the API.- In the app, the model actually used only shows up inside each run's session config JSON (
AppData/Roaming/Claude/claude-code-sessions/.../<session>.json,modelfield). Changing the model on a session (or a fork) does not reliably repilot future scheduled runs.
Result: users can't audit or control the per-routine model choice. With 20+ routines this matters for cost (Haiku vs Sonnet vs Opus) and quality.
Request
- Display each scheduled task's model — in the routines list / task detail, and in
list_scheduled_tasksoutput. - Set / update it — a
modelfield onupdate_scheduled_task, and a model selector in the routine settings that persists to future runs.
Why it matters
- Cost tuning: route simple digests to Haiku, reasoning-heavy routines to Sonnet/Opus.
- Easy migration when a new model ships (e.g. Sonnet 4.6 → Sonnet 5): today there's no reliable way to switch a routine's model.
Related: #64843 (also area:routines — scheduled task sessions not shown under the Scheduled sidebar section).
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗