@codeam/shared 2.61.50 → 2.61.52

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.mjs CHANGED
@@ -355,13 +355,12 @@ var AGENT_REGISTRY = {
355
355
  displayName: "opencode",
356
356
  binaryName: "opencode",
357
357
  enabled: true,
358
- // opencode auth = `opencode auth login` (multi-provider; API keys AND
359
- // provider OAuth), which writes a login-state file at
360
- // ~/.local/share/opencode/auth.json. The CLI captures that blob (like
361
- // claude/codex capture their local login), so the vaulted credential is
362
- // the auth.json — an `oauth_token`-kind login blob, not a bare api_key.
363
- supportedAuthKinds: ["oauth_token"],
364
- preferredAuthKind: "oauth_token",
358
+ // opencode is model-AGNOSTIC and AUTO-DETECTS provider API keys from env
359
+ // vars (ANTHROPIC_API_KEY / OPENAI_API_KEY / GEMINI_API_KEY / …) — same
360
+ // model as aider. So the credential is the user's OWN provider key; we set
361
+ // the matching env var (detected by prefix) at deploy. api_key only.
362
+ supportedAuthKinds: ["api_key"],
363
+ preferredAuthKind: "api_key",
365
364
  // Not listed by `headroom init --global` (claude/codex/copilot only) — native.
366
365
  headroomWrappable: false,
367
366
  // Native ACP server: `opencode acp` (stdio JSON-RPC).
@@ -1106,6 +1105,37 @@ var INTEGRATION_REGISTRY = {
1106
1105
  httpHeaders: { "X-Goog-Api-Key": "{accessToken}" }
1107
1106
  }
1108
1107
  }
1108
+ },
1109
+ vercel: {
1110
+ id: "vercel",
1111
+ name: "Vercel",
1112
+ icon: "vercel",
1113
+ category: "deployment",
1114
+ // DARK — OAuth (PKCE public client). The user authorizes our registered
1115
+ // Vercel OAuth app; the access token calls Vercel's OFFICIAL hosted remote
1116
+ // MCP (mcp.vercel.com, Streamable HTTP) as a Bearer header — the SAME shim
1117
+ // HTTP transport as PostHog/Datadog. Vercel MCP is approved-clients + per-
1118
+ // connection OAuth consent, but that consent is the ONE-TIME authorize (not
1119
+ // per MCP request), so a backend-brokered access token works headless.
1120
+ // Endpoints (from mcp.vercel.com/.well-known/oauth-protected-resource →
1121
+ // vercel.com/.well-known/oauth-authorization-server): authorize
1122
+ // https://vercel.com/oauth/authorize, token
1123
+ // https://vercel.com/api/login/oauth/token, PKCE S256, token-endpoint auth
1124
+ // 'none' (public). enabled:false until Step-8 live-verify of the Bearer.
1125
+ enabled: false,
1126
+ auth: {
1127
+ kind: "oauth_redirect",
1128
+ scopes: ["openid", "offline_access"]
1129
+ },
1130
+ delivery: {
1131
+ mcp: {
1132
+ command: "",
1133
+ args: [],
1134
+ envMapping: {},
1135
+ httpUrl: "https://mcp.vercel.com",
1136
+ httpHeaders: { Authorization: "Bearer {accessToken}" }
1137
+ }
1138
+ }
1109
1139
  }
1110
1140
  };
1111
1141
  function getEnabledIntegrations() {