Repository navigation
feat(openrouter): trace GA and beta Responses APIs - #893
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5bd2bfb84d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".
|
|
||
| class ResponsesSendPatcher(FunctionWrapperPatcher): | ||
| name = "openrouter.beta.responses.send" | ||
| name = "openrouter.responses.send" |
There was a problem hiding this comment.
Keep legacy Responses spans labeled as beta
With the supported OpenRouter 0.6.0 release, client.beta.responses is backed by openrouter.responses.Responses, while openrouter.beta_responses is unavailable. Consequently, package-level OpenRouterIntegration.setup() and auto_instrument() select this renamed patcher and now emit openrouter.responses.send for the beta API; only manual wrap_openrouter() selects BetaResponsesPatcher, so the new tests miss this entry-point mismatch. Version-gate this patcher or retain a legacy beta wrapper for the old module layout.
AGENTS.md reference: AGENTS.md:L134-L141
Useful? React with 👍 / 👎.
client.responses.sendandsend_asyncthroughwrap_openrouter().BetaResponsesclass when the module is available, while retaining OpenRouter 0.6.0 support.Closes #860