Add default-off GPT-5.6 Ultra agent mode#44
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
runtime.ultra, defaulting tofalse, and map logical Ultra requests to the supportedmaxwire effortUser and developer impact
Normal installs retain existing behavior because Ultra is disabled by default. Enabling
runtime.ultraexposes Ultra only for eligible live-catalog models. The old managedorchestrator.md, collaboration headers, and prompt cache are removed; the coreFetchOrchestratorretry and account-rotation engine is unchanged.Safety and compatibility
Validation
npm run verifynpm run check:upstreamnpm pack --dry-run --jsonRelease
Planned as
v1.9.0after merge and green push CI onmain, using the repository-nativenpm run release:minorflow.