mirror of
https://github.com/expo/code-review-cli.git
synced 2026-11-15 17:30:42 -10:00
* Mixed Codex-subscription + API-key auth; GPT by default; report each pass's model - auth accepts a per-provider map (auth.providers) alongside the legacy single object; upstream aliases synthesize OpenCode provider blocks so one upstream is reachable with two credentials at once (subscription for default models, metered key for the pro tier the subscription excludes) - openai oauth stores the REFRESH token (expires 0; OpenCode's codex plugin mints access tokens; reuse across runs verified) - tokenEnv guard (verify-config) + runtime lock use exact SET semantics via comma-separated ECR_EXPECTED_TOKEN_ENV - default model is openai/gpt-5.5; anthropic subscription OAuth removed from docs (prohibited upstream and unsupported by OpenCode; API key still works) - an empty REVIEWER_MODEL no longer wipes configured model ids - every pass reports the provider/model that ACTUALLY answered (job log, step summary table, run log agentModels) and warns loudly on substitution — reviews silently ran on opencode's free gateway model for weeks behind the two failures above - this repo's own review runs the mixed setup (security on openai-api/gpt-5.5-pro) * Close the cross-provider key redirect; default the expected set to both names Review findings on this PR (the pro-tier security pass, fittingly): - a well-known provider key env may only feed the provider that owns it — the tokenEnv guard locks NAMES, so without this an auth entry could keep a locked name but point provider/upstream at a different provider - the self-review workflow's ECR_EXPECTED_TOKEN_ENV fallback now matches the committed two-credential config instead of relying on the repo variable