Repository navigation
Promote Opus capability fixes and 0.1.25 to main - #93
Merged
Merged
Conversation
fix: restore native Opus limits and thinking continuity
pavelhov
changed the title
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.
Promote the qualified Opus 5.5 fixes from development to main for CodexCommander 0.1.25 (build 2026102303).
The failure after 0.1.24 was confirmed as an ordinary native Codex turn, which omitted an output limit and received the legacy 40,192-token total. Native Opus ordinary turns now default to 128,000 total output tokens, the catalog exposes 1M context with a 900K default compaction threshold, and signed/redacted thinking survives JSON/SSE and terminal-guard tool continuation. Explicit budgets, requested ordinary effort, smaller live/explicit context limits, custom gateways and the 64K/medium compaction policy retain their semantics. Existing Codex clients must reload the refreshed catalog.
Source commits: ba2e3fc (runtime, regressions and documentation), 38b11cc (version 0.1.25); feature PR #92 merged at 2dd2d87. Development's tree matches the qualified source 38b11cc.
Validation: all 633 Bun test files passed; typecheck/privacy passed; GUI lint/i18n, 888 tests and build passed; docs built 44 pages; CLI smoke passed. Required feature, promotion and main CI passed. Six isolated real Sparkle updates from 0.1.24 passed stopped, native and owned runtime paths, active-Later, and both active-Anyway paths. The replaced bundles verified all ten changed module hashes, unchanged compaction transport, output policies, 1M/900K catalog, Models URL and thinking/tool continuity. Fixture cleanup verified zero fixture processes/services and removed disposable keys/preferences. Both universal slices were verified; Rosetta execution was not run. No live paid inference was used.
Security review: native metadata matching does not choose credential/routing destinations; authentication and transport ownership remain unchanged. Signature lifecycle has bounded retained/transient accounting and rejects unfinished thinking. No request-body, credential or account logging was added. Dependencies, workflows and release-distribution code are unchanged. The universal archive remains an ad-hoc, unnotarized preview. The existing external Ed25519 anchor authenticated the complete 20-item feed and immutable archive inventory. Fresh draft and unauthenticated public downloads matched the canonical bytes; the signed feed and all referenced archives passed verification. Release v0.1.25 is published as latest.
Archive SHA-256: 04c8a23867f52300b655fef35e6dce5903e3567529ecc33e1411c6d00188d59f.