fix: support Codex hosted tool routes#73
Merged
Conversation
- allowed tokenless local model discovery - routed hosted web search through Codex OAuth - classified unsupported OpenAI-compatible endpoints clearly - added regression coverage for proxy authentication boundaries
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
/v1/modelswithout CQ proxy credentials/alpha/searchthrough Codex OAuthRoot cause
Codex Desktop hosted tools honour
openai_base_urlbut do not know CQ's local proxy token. Requests outside existing native Codex handlers fell through to generic Claude proxy authentication and returned403 invalid proxy token.Impact
Web search and model discovery now use local Codex-compatible routing. Unsupported OpenAI endpoints return a clear
501instead of a misleading authentication failure.Verification
go build ./...go vet ./...go test -race -count=1 ./...