claude-code - 💡(How to fix) Fix Scheduled tasks ignore model setting, always run on Sonnet 4.6 [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48976Fetched 2026-04-17 08:54:15
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
0
Timeline (top)
labeled ×4commented ×2cross-referenced ×2
RAW_BUFFERClick to expand / collapse

Bug Description

Scheduled tasks always run on Sonnet 4.6 regardless of model configuration. The model setting is not respected through any available mechanism.

Steps to Reproduce

  1. Set "model": "claude-opus-4-6" in ~/.claude/settings.json
  2. Create a scheduled task via create_scheduled_task API
  3. In the Desktop app UI, confirm the task's model is set to Opus 4.6 (via Edit form)
  4. Also tried adding model: claude-opus-4-6 to the SKILL.md frontmatter
  5. Run the task (either via "Run now" or wait for cron trigger)

Expected Behavior

The task should run using Claude Opus 4.6 as configured.

Actual Behavior

The task always runs on Sonnet 4.6 (visible in the bottom-right corner of the task session window showing "Sonnet 4.6 · High"), regardless of:

  • Global settings.json model setting
  • UI Edit form model picker selection
  • model field in SKILL.md frontmatter (which gets stripped on some tasks)

Environment

  • Claude Code Desktop App (macOS)
  • Model set to claude-opus-4-6 globally
  • Multiple scheduled tasks affected

Impact

Users who need Opus-level reasoning for automated tasks (e.g., code auditing, development, multi-step agentic workflows) cannot configure scheduled tasks to use their preferred model. This is especially impactful for unattended automation where the user cannot intervene.

Additional Context

  • The create_scheduled_task and update_scheduled_task APIs do not expose a model parameter
  • The SKILL.md frontmatter model field is either stripped or ignored
  • The documentation states model can be changed "through the Edit form or ask Claude", but neither method persists the change to actual runtime

extent analysis

TL;DR

The issue can be mitigated by exploring alternative methods to set the model for scheduled tasks, as the current configuration mechanisms are not respected.

Guidance

  • Investigate the create_scheduled_task and update_scheduled_task APIs for any hidden or undocumented parameters that could allow setting the model.
  • Verify if there are any other configuration files or environment variables that could override the settings.json model setting.
  • Check the Desktop app UI for any other model selection options that might be specific to scheduled tasks.
  • Consider reaching out to the developers or support team for clarification on the intended behavior and potential workarounds.

Example

No code snippet is provided as the issue does not imply a specific code-based solution.

Notes

The issue seems to be related to a limitation or bug in the current implementation, and a proper fix might require changes to the API or the Desktop app. The provided guidance is focused on exploring potential workarounds.

Recommendation

Apply workaround: Given the lack of a clear solution, exploring alternative configuration methods or reaching out to the support team seems to be the most viable option.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING