fix: separate env vars for opencode-zen and opencode-go providers (closes #627) (#631)

Use independent OPENCODE_ZEN_API_KEY and OPENCODE_GO_API_KEY
instead of shared OPENCODE_API_KEY, preventing cross-provider config coupling.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
ekko
2026-05-11 21:03:47 +08:00
committed by GitHub
parent b4a80aceeb
commit bb639a9121
@@ -28,8 +28,8 @@ export const PROVIDER_ENV_MAP: Record<string, { api_key_env: string; base_url_en
kilocode: { api_key_env: 'KILO_API_KEY', base_url_env: '' },
'ai-gateway': { api_key_env: 'AI_GATEWAY_API_KEY', base_url_env: '' },
cliproxyapi: { api_key_env: '', base_url_env: '' },
'opencode-zen': { api_key_env: 'OPENCODE_API_KEY', base_url_env: '' },
'opencode-go': { api_key_env: 'OPENCODE_API_KEY', base_url_env: '' },
'opencode-zen': { api_key_env: 'OPENCODE_ZEN_API_KEY', base_url_env: '' },
'opencode-go': { api_key_env: 'OPENCODE_GO_API_KEY', base_url_env: '' },
huggingface: { api_key_env: 'HF_TOKEN', base_url_env: '' },
arcee: { api_key_env: 'ARCEE_API_KEY', base_url_env: '' },
stepfun: { api_key_env: 'STEPFUN_API_KEY', base_url_env: '' },