feat(zed): add Zed Hosted AI provider support by AMSeify · Pull Request #2823 · decolua/9router

AMSeify · 2026-07-25T08:31:36Z

Summary

Add Zed Hosted AI (cloud.zed.dev) as an OAuth provider: registry, executor, OpenAI↔Zed translators, and live model catalog
Wire dashboard auth (browser RSA OAuth + credential import), LLM token mint via zedAuth, and MITM CLI capture for Zed credentials
Fix /completions 500: restore snake_case CompletionBody.provider wire tags (anthropic, open_ai, google, x_ai) — PascalCase values parse but fail at runtime
Add ZedOAuthWrapper (browser vs import), OAuth session/callback fixes, plan-aware empty-catalog messages, and unit tests (tests/unit/zed-constants.test.js)
Synced with upstream master v0.5.55
Quota: show Zed plan / edit-prediction usage on /dashboard/quota (also feat(usage): show Zed plan quota on the dashboard #3407)

Test plan

Connect a Zed account from the provider dashboard (browser OAuth and manual import)
Zed provider page loads live /models catalog (student/Pro accounts)
Send a /v1/chat/completions request through a Zed model and confirm streaming works
cd tests && npx vitest run unit/zed-constants.test.js unit/zed-usage.test.js
OAuth URL baseline: node tests/__baseline__/verify-oauth-urls.mjs
Optional: exercise MITM capture path for Zed CLI traffic
Open /dashboard/quota with a connected Zed account and confirm plan + edit-prediction rows

Wire Zed cloud.zed.dev into the gateway so users can import Zed Editor credentials, mint/refresh LLM tokens, and route OpenAI-compatible chat through Zed's hosted models. Closes decolua#2821. Co-authored-by: Cursor <cursoragent@cursor.com>

sunba91-su · 2026-07-25T13:22:52Z

+  if (/(claude|anthropic)/i.test(m)) return "anthropic";
+  if (/(gemini|google)/i.test(m)) return "google";
+  if (/(grok|x[_-]?ai)/i.test(m)) return "x_ai";


Hardcoded model-routing regex — should use config constants.
Per open-sse/AGENTS.md : "NEVER hardcode values, models, or block/role strings — use config/ + schema/ constants."
These provider-detection rules should live in open-sse/config/ (e.g. a zedProviderPatterns map in the Zed provider config), not inline in the translator.

sunba91-su · 2026-07-25T13:26:07Z

+  async refreshCredentials(credentials, log, proxyOptions = null) {
+    const psd = credentials?.providerSpecificData || {};
+    const userId = psd.userId;
+    const zedAccessToken = psd.zedAccessToken || credentials?.refreshToken;
+    const organizationId = psd.organizationId;
+    if (!userId || !zedAccessToken) {
+      log?.warn?.("TOKEN_REFRESH", "Zed missing userId/zedAccessToken for LLM token refresh");
+      return null;
+    }
+    try {
+      const base = (this.config.baseUrl || "https://cloud.zed.dev").replace(/\/$/, "");
+      const path = PROVIDER_OAUTH.zed?.llmTokensPath || "/client/llm_tokens";
+      const body = organizationId ? { organization_id: organizationId } : {};
+      const res = await proxyAwareFetch(`${base}${path}`, {
+        method: "POST",
+        headers: {
+          Authorization: `${userId} ${zedAccessToken}`,
+          "Content-Type": "application/json",
+          Accept: "application/json",
+        },
+        body: JSON.stringify(body),
+      }, proxyOptions);
+      const text = await res.text();
+      if (!res.ok) {
+        log?.error?.("TOKEN_REFRESH", `Zed LLM token refresh failed (${res.status}): ${text.slice(0, 200)}`);
+        return null;
+      }
+      const data = JSON.parse(text);
+      const raw = data?.token;
+      const token =
+        typeof raw === "string"
+          ? raw
+          : raw && typeof raw === "object"
+            ? raw["0"] || raw.token || Object.values(raw)[0]
+            : null;
+      if (!token) return null;
+      return {
+        accessToken: token,
+        expiresIn: 3600,
+        providerSpecificData: {
+          llmToken: token,
+          lastLlmTokenAt: new Date().toISOString(),
+        },
+      };
+    } catch (err) {
+      log?.error?.("TOKEN_REFRESH", `Zed LLM token refresh failed: ${err.message}`);
+      return null;
+    }
+  }


Duplicated token refresh logic
ZedExecutor.refreshCredentials() and refreshZedToken() in tokenRefresh/providers.js contain near-identical logic:

Same HTTP call to POST /client/llm_tokens

Same Authorization header format (${userId} ${zedAccessToken})

Same CBOR-ish token unwrap (raw["0"] || raw.token || Object.values(raw)[0])

A bug fix to one won't propagate to the other. Recommendation: have ZedExecutor.refreshCredentials() delegate to refreshZedToken() from tokenRefresh/providers.js, or extract the shared HTTP+unwrap logic into ZedService.refreshLlmToken() (which already exists in src/lib/oauth/services/zed.js:164) and call it from both places.

sunba91-su · 2026-07-25T13:29:50Z

+  // OpenAI chat.completion.chunk
+  if (event.choices?.[0]) {
+    const choice = event.choices[0];
+    const delta = choice.delta || choice.message || {};


Missing tool_call/tool_use handling — breaks agent workflows
The response parser handles choices.delta, Responses API, Gemini, and Anthropic content shapes, but has no branch for tool_calls or tool_use content blocks.

When a Zed-hosted model returns tool calls (Claude tool_use, OpenAI tool_calls), they'll be silently dropped. This breaks multi-turn agent conversations (Claude Code, Codex, Cline, etc.) that rely on tool-call round-trips.

At minimum, pass through tool_calls/tool_use deltas unchanged so downstream handlers can process them. Other executors (cursor, kiro) handle this — worth checking their implementations for the right pattern.

Move model→provider patterns into zedConstants, delegate executor token refresh to refreshZedToken, pass through/convert tool_calls/tool_use in the JSONL→SSE parser, and regenerate registry/index.js. Co-authored-by: Cursor <cursoragent@cursor.com>

AMSeify · 2026-07-25T15:56:59Z

Addressed review feedback in 1e714e4:

Model-routing regex → moved to open-sse/config/zedConstants.js (ZED_PROVIDER_PATTERNS / resolveZedProvider)
Duplicated token refresh → ZedExecutor.refreshCredentials() now delegates to shared refreshZedToken() (also accepts proxyOptions)
tool_calls / tool_use → JSONL→SSE/JSON parser now passes through OpenAI tool_calls and converts Anthropic tool_use, Gemini functionCall, and Responses API function-call events
registry/index.js → regenerated from the registry directory (alphabetical static import list)

Diba-k · 2026-07-25T16:13:06Z

it works finely without any problem

Upstream landed RSA native-app Zed auth (zedAuth, OAuthModal, executor). Keep complementary CLI import/MITM, route provider patterns through zedConstants, unhide Zed in the registry, and align import credentials with the long-lived user-token shape expected by zedLlmFetch.

AMSeify · 2026-08-02T09:27:14Z

Synced this branch with upstream master (now mergeable).

Context: Upstream already landed Zed via RSA native-app OAuth (open-sse/shared/zedAuth.js, OAuthModal, multi-format executor). This PR is now aligned on top of that.

What this PR still adds / adjusts:

Provider routing constants — model→Zed upstream provider tags live in open-sse/config/zedConstants.js (addresses earlier review on hardcoded regex)
Unhide Zed in the registry so it appears in the providers list
CLI import + MITM kept as complementary auth paths; import now stores the long-lived user token (same shape as RSA OAuth) so zedLlmFetch mints LLM tokens on demand
Dashboard Connect uses upstream OAuthModal (RSA flow) instead of the import-only modal
Token refresh documents that LLM bearer refresh happens inside zedAuth (no duplicated HTTP refresh path)

Ready for another look @sunba91-su.

PascalCase CompletionBody.provider values caused opaque /completions 500s; restore HTTP wire tags (anthropic/open_ai) and align headers with the working executor path. Add ZedOAuthWrapper, live model catalog, OAuth callback fixes, plan-aware empty-catalog messages, and unit tests for the wire protocol. Co-authored-by: Cursor <cursoragent@cursor.com>

Register a /client/users/me handler so connected Zed accounts appear on /dashboard/quota with edit-prediction usage, plan labels, and unlimited rows. Co-authored-by: Cursor <cursoragent@cursor.com>

AMSeify · 2026-08-18T06:25:16Z

Synced this branch with upstream master at v0.5.55 (# v0.5.55 (2026-08-14)). Merge is clean again.

Also stacked Zed quota tracking (feat(usage): show Zed plan quota on the dashboard) so connected Zed accounts show up on /dashboard/quota. That work is also in a standalone PR against current master: #3407 (issue #3406).

Ready for another look @decolua @sunba91-su.

sunba91-su suggested changes Jul 25, 2026

View reviewed changes

AMSeify and others added 4 commits August 5, 2026 10:55

Merge branch 'master' into feat/zed-hosted-ai-provider

8065f13

merge(master): sync Zed PR with upstream v0.5.55

e70b452

feat(usage): show Zed plan quota on the dashboard

48ce9f1

Register a /client/users/me handler so connected Zed accounts appear on /dashboard/quota with edit-prediction usage, plan labels, and unlimited rows. Co-authored-by: Cursor <cursoragent@cursor.com>

This was referenced Aug 18, 2026

feat(usage): show Zed Hosted AI quota on the dashboard #3406

Open

feat(usage): show Zed plan quota on the dashboard #3407

Open

Navigation Menu

feat(zed): add Zed Hosted AI provider support - #2823

feat(zed): add Zed Hosted AI provider support#2823
AMSeify wants to merge 7 commits into
decolua:masterfrom
AMSeify:feat/zed-hosted-ai-provider

AMSeify commented Jul 25, 2026 •

edited

Loading

Uh oh!

sunba91-su Jul 25, 2026

Uh oh!

sunba91-su Jul 25, 2026

Uh oh!

sunba91-su Jul 25, 2026

Uh oh!

Uh oh!

AMSeify commented Jul 25, 2026

Uh oh!

Diba-k commented Jul 25, 2026

Uh oh!

AMSeify commented Aug 2, 2026

Uh oh!

AMSeify commented Aug 18, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

AMSeify commented Jul 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test plan

Uh oh!

sunba91-su Jul 25, 2026

Choose a reason for hiding this comment

Uh oh!

sunba91-su Jul 25, 2026

Choose a reason for hiding this comment

Uh oh!

sunba91-su Jul 25, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

AMSeify commented Jul 25, 2026

Uh oh!

Diba-k commented Jul 25, 2026

Uh oh!

AMSeify commented Aug 2, 2026

Uh oh!

AMSeify commented Aug 18, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

AMSeify commented Jul 25, 2026 •

edited

Loading