Repository navigation
feat(gateway): rename the SSO provider to AIGW - #340
Merged
Merged
Conversation
New SSO sign-ins write the gateway provider as aigw, labeled AIGW. The pre-rename netgate id stays recognized everywhere (candidate sets, the inline-key migration, the upload readers, the sign-in nudge), and the desktop's silent key refresh now re-keys legacy ids too, so pre-rename configs keep working and converge on the new id at their next full config rewrite. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.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
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.
What
The SSO-issued gateway identity is renamed from
netgate/ "netGate" toaigw/ "AIGW". New sign-ins (TUI/configure, desktop sign-in, sandbox guest configs) writeprovider.aigwblocks labeled AIGW in the model picker.Companion hub PR renames the same identity in codev-hub so hub-managed and self-configured installs stay indistinguishable.
Back-compat
Follows the established pattern from the previous identity rename (
aigateway→netgate): the old id stays recognized, nothing writes it any more, and configs converge on the new id at their next full rewrite.LEGACY_GATEWAY_PROVIDER_IDS = ["netgate"]in@codev/gateway.["aigw", "netgate", "ai-gateway", "aigateway"]: the startup inline-key migration (gateway-key-migration.ts) and the upload readers (codev-upload/src/config.ts), mirroring the hub's probe set.ensureKeynow returnsproviderIDs(current + legacy ids) and the renderer writes the re-minted key under each, so a pre-renameprovider.netgateblock keeps getting fresh credentials instead of 401ing when its short-lived key expires.A user who re-runs a codev-code configure flow on a legacy install gets an
aigwblock merged beside the lingeringnetgateone (config PATCH is a deep merge and cannot delete); both keep working, and a hub-managed install converges fully on its next hub configure/refresh, which rewrites the file wholesale.Tests that pin legacy recognition (upload base-URL readback, inline-key migration, the nudge) deliberately keep
netgatefixtures; identity-pinning tests moved toaigw/AIGW.Verification
bun typecheckclean incodev-gateway,codev-upload,desktop,app,opencode,tuiprovider.test.tsunder suite load passed on re-run and reproduces without these changes)🤖 Generated with Claude Code