Describe the feature or problem you'd like to solve
Currently, in Auto mode, the active model (and therefore context window size, e.g., 128K vs 1M) is chosen automatically per turn with no visible way to pin a session/turn to a specific context window tier. This makes it hard to plan for large-context workflows (big diffs, long codebases, big review sessions) since: 1. There's no setting ( /settings , /config ) to default Auto to prefer 1M-context models when available. 2. /model requires manually picking a specific model each session; this choice isn't "sticky" across Auto reselection. 3. /context shows current usage but doesn't indicate whether a larger-context alternative exists for the same task
Proposed solution
Suggestion: Add a session/user-level preference (e.g., /settings context=large ) that biases Auto toward 1M-context-capable models when the task or repo size warrants it, and surface in /context whether a bigger-context model is available.
Example prompts or workflows
No response
Additional context
No response
Describe the feature or problem you'd like to solve
Currently, in Auto mode, the active model (and therefore context window size, e.g., 128K vs 1M) is chosen automatically per turn with no visible way to pin a session/turn to a specific context window tier. This makes it hard to plan for large-context workflows (big diffs, long codebases, big review sessions) since: 1. There's no setting ( /settings , /config ) to default Auto to prefer 1M-context models when available. 2. /model requires manually picking a specific model each session; this choice isn't "sticky" across Auto reselection. 3. /context shows current usage but doesn't indicate whether a larger-context alternative exists for the same task
Proposed solution
Suggestion: Add a session/user-level preference (e.g., /settings context=large ) that biases Auto toward 1M-context-capable models when the task or repo size warrants it, and surface in /context whether a bigger-context model is available.
Example prompts or workflows
No response
Additional context
No response