Expand Codex protocol and plugin compatibility#5
Draft
hereww wants to merge 1 commit into
Draft
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.
What changed
Why
Recent Codex app and provider variants use different protocol, marketplace, and local-state layouts. These changes keep CodexTools compatible across those variants while preserving tool calls, reasoning output, plugin discovery, session actions, and script state.
Impact
Users can route Responses API requests through Chat Completions-compatible providers, use the bundled official remote plugin marketplace, and manage sessions and scripts consistently across current Codex layouts.
Validation
go test ./...npm --prefix web run checknpm --prefix web run vite:buildgit diff --cached --checkunzip -t