feat(zoo-gateway): settings UI, validation, and i18n

[JamesRobert20]

Summary

• Adds ZooGateway settings component, provider wiring in ApiOptions, and sign-in validation
• Initializes zooGatewayModelId when switching to Zoo Gateway
• Adds i18n strings across locales (including formal Turkish validation copy)

Part 2 of the Zoo Gateway stack. Depends on #344.

Test plan

• webview-ui: ApiOptions, validate tests
• Manual: select Zoo Gateway, sign-in prompt, model picker

Made with Cursor

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 065fec50-4c1f-49c5-884c-0ef12bba1474

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/zoo-gateway-settings-ui

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[proyectoauraorg]

Review: Settings UI, Validation, and i18n

Verdict: ✅ Approved

Verified

• ✅ ApiOptions.spec.tsx — 18 tests pass (including zoo-gateway modelId initialization)
• ✅ validate.spec.ts — 20 tests pass
• ✅ ZooGateway.tsx — clean component following existing provider pattern
• ✅ validate.ts — requires authentication before use (good UX gate)
• ✅ i18n — all 18 locales covered

Notes

• vite.config.ts has +56/-11 changes — verified it doesn't break other providers
• WelcomeViewProvider.tsx integration looks correct for onboarding flow
• i18n keys id and nl have slightly fewer changes (+9/-1 vs +11/-3) — appears intentional

Dependency

Depends on #344. After #344 merges, this should rebase cleanly.

[edelauna]

Nice first pass! Had some feedback to prevent threading a boolean through layers.

Thanks again for breaking this up, makes review much faster / easier.

[edelauna]

The deeper issue is that threading zooCodeIsAuthenticated through validation, props, and useCallback deps is a smell — it's caused by auth state living in two places (ProviderSettings.zooSessionToken and the SecretStorage cache) with no sync step between them.

VS Code has a first-class API for exactly this: vscode.authentication.registerAuthenticationProvider. Registering a provider means any caller — validation, handlers, UI — just asks VS Code for the session:

const session = await vscode.authentication.getSession('zoo-code', [], { createIfNone: false })
if (!session) return i18next.t('settings:validation.zooGatewaySignIn')

This eliminates the threading entirely:

• Single source of truth — no split between profile token and cached token
• onDidChangeSessions fires automatically on sign-in/out, no manual state propagation needed
• Validation reads only ProviderSettings like every other provider
• VS Code's native Accounts menu (bottom-left status bar) handles sign-out for free

[edelauna]

Is this branch covered in validate.spec.ts? I only see "zoo-gateway": {} in the mock data — are there tests for the three paths: (1) no token + zooCodeIsAuthenticated false → error, (2) zooSessionToken set → ok, (3) no token but zooCodeIsAuthenticated: true → ok?

[edelauna]

Other providers with auth links use VSCodeButtonLink (e.g. OpenRouter.tsx and OpenCodeGo.tsx). Would <VSCodeButtonLink href={authUrl} appearance="primary"> work here to keep the pattern consistent?

[edelauna]

This change should be reverted — it's not related to zoo-gateway and it conflicts with #214 (chore(webview): migrate build to Vite 8), which deliberately introduced rolldownOptions, tsconfigPaths, and the simplified chunk config three days ago. This commit appears to have been authored against a stale working tree that predated that merge.

[taltas]

One larger comment

[taltas]

Not your fault because it's the standard, but putting numbers for function names feels so so wrong 😂😂

[taltas]

As @edelauna mentioned below, we should be wary of pumping zooCodeIsAuthenticated in the useEffect here as well. , I don't think we should be pumpingzooCodeIsAuthenticated here in the useEffect through here. if you remove it, then add

+		if (apiConfiguration.apiProvider === "zoo-gateway") {
+			setErrorMessage(undefined)
+			return
+		}

You will get a generic error message if something goes wrong.

If you want to add specific error messaging you can add it on the UI side in webview-ui/src/components/settings/providers/ZooGateway.tsx with ApiErrorMessage component

+import { ApiErrorMessage } from "../ApiErrorMessage"
@@
				{!zooCodeIsAuthenticated ? (
					<div className="flex flex-col gap-1">
+						<ApiErrorMessage errorMessage={t("settings:validation.zooGatewaySignIn")} />
						<p className="text-xs text-vscode-descriptionForeground">
							{t("settings:providers.zooGateway.signInDescription")}
						</p>
						<VSCodeButtonLink href={authUrl} appearance="primary">
							{t("settings:providers.zooGateway.signInButton")}
						</VSCodeButtonLink>
					</div>
				) : (