Repository navigation
[STALE: REBASE FROM NEW FORK] AgentRadar account pin admits Copilot, Cursor and Devin sign-ins (.22) - #20
Open
vadymhimself wants to merge 1 commit into
Conversation
…vin sign-ins (.22) AgentRadar AGE-2323 (Vadym 21431, "Let them in too") adds hosted sign-ins for GitHub Copilot, Cursor and Devin next to Claude, ChatGPT, Grok and Kimi. Every hosted turn carries the x-agentradar-account-pin header, and the gateway refused any pin provider other than claude, codex, grok or kimi, so a signed-in Copilot, Cursor or Devin account could never serve a pinned turn. The pin's provider names now come from one table, AGENTRADAR_PIN_PROVIDERS, which maps each AgentRadar sign-in name to the OCX OAuth provider whose stored account it may serve (copilot -> github-copilot, cursor -> cursor, devin -> devin). The header parser and the route check in prepareResponsesRequest both read it, so they cannot drift. Codex keeps its own pool path. The check is otherwise unchanged: only an oauth candidate of exactly that provider serves the pin, so a pin never reaches another provider's account or an API key. Tests: tests/server/agentradar-account-pin-e2e.test.ts adds a github-copilot provider with two accounts. A copilot pin on the second-listed account serves with that account's token while the active account stays the other one, and a copilot pin on a kimi route is refused before any inference. Copilot, Cursor and Devin pins all join the cross-provider refusal loop. Co-Authored-By: Claude Code <noreply@anthropic.com>
|
✅ Deterministic PR hygiene checks passed. |
Collaborator
Author
|
This PR is based on the superseded 2.65 gateway line. Rebuild the change from |
This branch has not been deployed
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.
AgentRadar AGE-2323 (Vadym 21431, "Let them in too"): hosted sign-ins for GitHub Copilot, Cursor and Devin. Stacked on #19 (.21); release tag .22.
What changes
Every hosted AgentRadar turn carries an account pin. The gateway accepted only claude, codex, grok and kimi pins, so a Copilot, Cursor or Devin sign-in could never serve a pinned turn.
AGENTRADAR_PIN_PROVIDERSinsrc/server/responses/core-options.tsmaps each AgentRadar sign-in name to the OCX OAuth provider it may serve: claude -> anthropic, grok -> xai, kimi -> kimi, copilot -> github-copilot, cursor -> cursor, devin -> devin. Codex keeps its own pool path.request-prepare.tsboth read that table.Tests
tests/server/agentradar-account-pin-e2e.test.ts:Bearer tcA), and the active account stayscB.Lane run (typecheck plus the pin e2e):
TSC=0, 3 pass, 0 fail.Not in this PR
This PR adds no provider login, no model list and no adapter change. The Copilot, Cursor and Devin bridges are already in the fork; they are labelled experimental or unofficial there, and that label is with the AgentRadar lead before any of them is offered to customers.
🤖 Generated with Claude Code