Repository navigation
feat: Claude and Codex parity for v2.4.0 - #116
Merged
Merged
Conversation
Unify sharing previews, finish provider interaction and localization parity, preserve legacy commands, and keep large histories and live scrolling bounded. Co-authored-by: OpenAI Codex <215057067+openai-codex[bot]@users.noreply.github.com>
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
Bring Codex out of Beta with the same navigation, chart drill-down, keyboard, accessibility, and visual interaction patterns as Claude, while preserving each provider's distinct token, price, cache, and quota semantics. Consolidate local sharing into one preview-first workspace, improve large-history and live-scroll behavior, and complete documentation for all eight UI languages. This branch is based on
mainafter #114 and #115, so their fixes and contributor attribution remain upstream rather than being duplicated here.Linked issues
Relates to #99. The append and memory regressions are covered, but the reported Windows CPU behavior has not been independently reproduced or declared fixed.
Type of change
fix(patch)feature(minor)breaking(major)docs/ci/chore(patch)How was this tested?
npm run test:release: 1,108 Node tests passed, one intentionally skipped; 182 Chromium UI tests passed, including both upstream date/index changes and the new provider-parity, sharing, narrow-screen, and accessibility regressions.@vscode/vsce4.0.0 and passed the repository's archive/payload verification (122 files). This exact combined artifact still needs maintainer installed-extension acceptance.Checklist
npm run compileis cleanI18nwith all eight UI locales filledCHANGELOG.mdupdated (user-visible changes)README.mdupdated if behaviour/settings changedThis is a reviewable candidate, not a published release. Remote CI and maintainer review remain gates before merging or release.
🤖 Generated with OpenAI Codex