Repository navigation
feat: Bump support for cursor SDK - #2742
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. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9cb93908b7
ℹ️ 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".
| body: args.responseBody.length | ||
| ? encodeBinaryDraft( | ||
| args.responseBody, | ||
| headerValue(args.responseHeaders["content-type"]), | ||
| ) |
There was a problem hiding this comment.
When a streamingRequests endpoint returns genuine text, JSON, or SSE containing credentials, encoding every nonempty response as a binary draft bypasses the default paranoid body redaction. applyResponseRedaction leaves binary drafts unchanged, whereas the previous bodyFromBytes path classified responses below the external-blob threshold as text/JSON/SSE and masked credential fields and token patterns. Such credentials are now persisted verbatim in committed blob sidecars. Preserve binary protobuf bytes without disabling redaction for supported textual streams, and keep chunk sizes consistent with any redacted payload.
Useful? React with 👍 / 👎.
No description provided.