fix(codexapp): capture standard Responses API paths - #422
Open
liaohch3 wants to merge 1 commit into
Open
Conversation
Allow Codex App forward-proxy sessions to persist standard /v1/responses traffic used by custom API providers while retaining the existing method and path filters. Co-authored-by: Talon <talon@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
1 participant
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
POSTand WebSocket traffic on the standard/v1/responsesendpoint used by custom API providers./backend-api/codex/responsescapture path and method restrictions.Problem
Codex App requests to providers such as MiniMax are relayed through the forward proxy at
/v1/responses, but the client-specific trace allowlist only included the ChatGPT backend path. These successful requests were therefore omitted from trace storage and the dashboard.Validation
uv run ruff check .uv run ruff format --check .uv run pytest tests/ -x --timeout=60(1073 passed, 26 skipped)uv run pytest tests/test_e2e.py::test_codex_upstream_url_construction -q --timeout=60uv run claude-tap --tap-client codexapp --tap-no-launchagainst a local upstream, sent a MiniMax-shapedPOST /v1/responsesthrough the forward proxy, and confirmed one SQLite trace record with HTTP 200.scripts/check_screenshots.shEvidence
The dashboard screenshot below comes from the real localhost
claude-tap --tap-client codexappproxy session backed by the captured SQLite trace.Fixes #415