Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Explicit control over model context window size

Open
#4,898 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Domain
ai, cli

Research direction

Start by tracing the /settings, /config, /model, and /context command entry points, then locate the Auto model-selection path. Done means the proposed preference can influence Auto selection and /context indicates when a larger-context alternative is available.

Written by the indexing model from the issue text.

Description

triage
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

Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/copilot-cli

All issues in github/copilot-cli

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.