Why is experimental Context Management limited to ChatGPT subscription sessions?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Regarding this release note:
Adds the disabled-by-default
features.context_management.experimental_modeconfiguration. When enabled for eligible ChatGPT Plus, Pro, or Pro Lite sessions using the Codex backend, it activates token-budget context, history notes, and thenew_contexttool. API-key sessions, custom providers, and temporary structured threads remain excluded. (#42385)
Is there a technical reason why API-key sessions are excluded from Context Management?
Since API-key sessions also use the Responses API, I’m wondering whether Context Management depends on any Codex-backend-specific capability that is not available through the public Responses API, or whether this is mainly a rollout/product restriction for now.
If it is only a rollout restriction, are there plans to support Context Management for API-key sessions in the future?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the quoted release note and issue #42385, then identify where experimental Context Management eligibility is defined for session types. Done means the issue has a maintainer-confirmed explanation of the API-key exclusion and any stated plan for future support.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100