feat(ai): provider and OAuth parity for /login#193
Open
islee23520 wants to merge 2 commits into
Open
Conversation
Add 18 API-key providers (alibaba-coding-plan, cursor, deepinfra, firepass, fugu, gitlab-duo, glm-zcode, kagi, kilo, kimi-code, litellm, lm-studio, minimax-code(-cn), moonshot, nanogpt, ollama(-cloud), openai-codex-device, parallel, perplexity, qianfan, qwen-portal, synthetic, tavily, venice, vllm, zenmux) plus OAuth flows for cursor, gitlab-duo, glm-zcode, google-antigravity, google-gemini-cli, kilo, kimi-code, openai-codex-device, perplexity, xai, and the remaining Gajae provider-ID gaps for full /login parity. The coding-agent provider wiring (model-resolver defaults, provider-display-names, auth-providers oauth-only set) travels here because model-resolver is exhaustive over the ai KnownProvider union. Source of truth for keys remains env-api-keys.ts; parity is enforced by test/api-key-provider-parity.test.ts.
Declare the API-key providers added for /login parity (alibaba-coding-plan, deepinfra, firepass, fugu, kagi, litellm, lm-studio, nanogpt, ollama, ollama-cloud, parallel, qianfan, qwen-portal, synthetic, tavily, venice, vllm, zenmux) across the three synchronized environment surfaces: .devcontainer/devcontainer.json secrets, scripts/devenv-setup.mjs PROVIDER_KEYS, and .agents/skills/senpi-qa/references/env-vars.md. Source of truth remains packages/ai/src/env-api-keys.ts.
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
Adds 18 API-key providers + OAuth flows (cursor, gitlab-duo, glm-zcode, google-antigravity, google-gemini-cli, kilo, kimi-code, openai-codex-device, perplexity, xai) and the remaining Gajae provider-ID gaps for full
/loginparity.packages/aionly, plus the coding-agent provider wiring (model-resolver,provider-display-names,auth-providers) that is exhaustive over the aiKnownProviderunion.Stack
Base unit of the auth split. The credential-broker and auth-gateway PRs stack on top of this branch.
Evidence
npm run checkgreen (biome, tsgo, shrinkwrap, install-lock, neo).packages/ai/src/env-api-keys.ts; parity enforced bytest/api-key-provider-parity.test.ts.Note: the only pre-existing
aitest failures are Cloudflare live-E2E tests that fail identically onmain(live CF endpoint errors in this environment) — unrelated to this PR.Note
This PR now also includes the synchronized environment-surface wiring (
.devcontainer/devcontainer.jsonsecrets,scripts/devenv-setup.mjsPROVIDER_KEYS,env-vars.md) — per the repo contract, those surfaces must trackenv-api-keys.ts, so they travel with the providers.