Repository navigation
feat(gateway): tell bouncer when a request runs on a ChatGPT subscription - #7820
Merged
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryThe PR adds an optional Verification notes
Files Reviewed (4 files)
Reviewed by deepseek-v4.1-flash · Input: 53.5K · Output: 7.5K · Cached: 593.8K Review guidance: REVIEW.md from base branch |
pandemicsyn
approved these changes
Oct 19, 2026
This was referenced Oct 19, 2026
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
Bouncer is adding a
siwc_poolrule. It flags payers who run on their own ChatGPT subscription ("Sign in with ChatGPT") and share one IP or JA4 digest. Bouncer can only learn that a request is SIWC from the usage event that Cloud sends. This PR makes Cloud send that fact.siwcfield.siwc: trueonly when the request routed to theopenai-chatgptprovider. Other requests omit the field. The wire body never sendsfalse.The deployed bouncer validates with typia
createValidate, so it accepts the extra field and ignores it until the bouncer change deploys. Cloud can ship first.Verification
processUsage.test.ts: a request with provideropenai-chatgptreportssiwc: true; the existing non-SIWC test now asserts that the field is absent.bouncer/client.test.ts: the wire body sendssiwconly when it istrue.Visual Changes
N/A
Reviewer Notes
No decide payload, UI, or DB change.