Let individual (non-org) accounts set their own default model — for new chats AND scheduled tasks (Cowork)
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Individual (non-organization) Pro/Max users have no setting to choose the default model that new conversations and scheduled tasks start on. The only "default model" control lives in Org/Team/Enterprise admin settings, which individual accounts cannot access. With no individual-facing control, the app auto-selects the default - currently Fable.
This bites hardest with scheduled tasks in Cowork: a scheduled task's INTERACTIVE chat model locks on its FIRST run. If the task auto-runs (scheduled) before the user manually opens it, it locks to the Default (= Fable) permanently - the user can never change the model they chat with for that task afterward. To get a non-Fable model, the user must manually first-run every task and pick a model before the schedule fires. For a fleet of 20+ tasks that is 20+ manual runs + 20+ model picks. The frontmatter model: controls the scheduled-RUN model correctly, but NOT the interactive-chat model, and there is no per-task persistent model field.
Proposed Solution
- Give INDIVIDUAL accounts a "default model" setting (mirroring the existing org-level one), in Settings, applying to new chats AND scheduled tasks.
- Make a scheduled task's model an editable, persistent property of the task (set once, applies to both scheduled runs and interactive chats) - not locked-on-first-run.
- Don't silently default to Fable; honor the task's
model:(or a per-task setting) for the interactive chat too.
Environment: Claude Desktop, Cowork mode, macOS, individual Max plan (no organization).
Related (distinct from these): #65476 is the managed/org-settings counterpart; this is the individual / non-org version. #62694 (/model picker respecting env vars) is CLI-oriented. #67372 (defaulting to Opus when Fable intended) and #66137 (/model selection not persisting) are related defaulting bugs.
Alternative Solutions
_No response_
Priority
High - Significant impact on productivity
Feature Category
Configuration and settings
Use Case Example
_No response_
Additional Context
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗