chore(web): remove dead OpenNext/Cloudflare machinery now that web is on Vercel

Web is hosted on Vercel, so strip the CF-web build/deploy artifacts from apps/web:
- scripts: build -> 'next build' (was opennext build); drop deploy/preview/upload/
  cf-typegen (web deploys via Vercel CI now).
- next.config: drop output:standalone + the OpenNext dev shim (pure Vercel build).
- delete apps/web/wrangler.jsonc + open-next.config.ts (dead).
(The @opennextjs/cloudflare + wrangler devDeps are now unused but left in place to
avoid lockfile churn right after a verified deploy; prune in a follow-up.)

Includes other in-tree changes: Composio tool-list hardening + doc updates.

Author: iamjr15

AGENTS.md

@@ -22,7 +22,7 @@ explicitly asks to delete the V1 code by name — see `plan.md` Section 20.
 | Database | Supabase Postgres via Hyperdrive + Drizzle 0.45.2 |
 | Auth | Clerk 7.3.4 |
 | Billing | Polar 0.46.4 |
-| OAuth tools | Composio `@composio/core@0.8.1` |
+| OAuth tools | Composio `@composio/core@0.10.0` |
 | Storage | R2 (no Supabase Storage) |
 | Observability | Workers Logs + Workers Tracing + Workers Analytics Engine (no third-party APM in V1) |
 | Lint/format | Biome 2.4 (single config, no ESLint+Prettier except next plugin) |

CLAUDE.md

@@ -21,7 +21,7 @@ Direct competitors: Manus (generalist async agent), HappyCapy (GUI workstation +
 | Database | **Supabase Postgres via Cloudflare Hyperdrive** + **Drizzle 0.45.2** (no `service_role` from Workers — uses `app_worker` role) |
 | Auth | **Clerk 7.3.4** (Workers JWT verify) |
 | Billing | **Polar 0.46.4** (no fixed cost, rev-share only) |
-| OAuth tool integrations | **Composio `@composio/core@0.8.1`** |
+| OAuth tool integrations | **Composio `@composio/core@0.10.0`** |
 | Storage | **R2** (no Supabase Storage; zero egress) |
 | Observability | **Cloudflare Workers Logs + Workers Tracing + Workers Analytics Engine** — no Sentry, no Langfuse, no Axiom |
 | Default models | Claude Sonnet 4.6 (code) / GPT-5.4 Thinking (reasoning) / GPT-5.4 Mini fallback |

apps/web/next-env.d.ts

@@ -1,6 +1,6 @@
 /// <reference types="next" />
 /// <reference types="next/image-types/global" />
-import "./.next/dev/types/routes.d.ts";
+import "./.next/types/routes.d.ts";
 
 // NOTE: This file should not be edited
 // see https://nextjs.org/docs/app/api-reference/config/typescript for more information.

apps/web/next.config.ts

@@ -8,20 +8,8 @@ const nextConfig = {
     qualities: [75],
     minimumCacheTTL: 14_400,
   },
-  // `standalone` is required by the OpenNext/Cloudflare build but conflicts with
-  // Vercel's managed output, so emit it everywhere EXCEPT Vercel builds.
-  ...(process.env["VERCEL"] ? {} : { output: "standalone" as const }),
 } satisfies NextConfig;
 
 const withNextIntl = createNextIntlPlugin("./src/lib/intl/request.ts");
 
 export default withNextIntl(nextConfig);
-
-// Local-dev only: wire OpenNext's Cloudflare binding shim for `next dev`. Loaded
-// via dynamic import behind a dev guard so production builds (incl. Vercel, which
-// has no @opennextjs/cloudflare and no CF runtime) never resolve it.
-if (process.env["NODE_ENV"] === "development") {
-  void import("@opennextjs/cloudflare")
-    .then((m) => m.initOpenNextCloudflareForDev())
-    .catch(() => undefined);
-}

apps/web/open-next.config.ts

@@ -5,14 +5,10 @@
   "type": "module",
   "packageManager": "pnpm@10.33.2",
   "scripts": {
-    "build": "next build --webpack && opennextjs-cloudflare build --skipNextBuild",
-    "cf-typegen": "wrangler types --env-interface CloudflareEnv cloudflare-env.d.ts",
-    "deploy": "CHEATCODE_REQUIRE_WEB_PUBLIC_ENV=true tsx ../../scripts/require-production-approval.ts && NEXT_PUBLIC_GATEWAY_URL=https://gateway.trycheatcode.com pnpm build && opennextjs-cloudflare deploy",
+    "build": "next build",
     "dev": "next dev --webpack",
     "lint": "biome check .",
-    "preview": "pnpm build && opennextjs-cloudflare preview -- --port 3001",
-    "typecheck": "tsc -p tsconfig.json --noEmit",
-    "upload": "CHEATCODE_REQUIRE_WEB_PUBLIC_ENV=true tsx ../../scripts/require-production-approval.ts && NEXT_PUBLIC_GATEWAY_URL=https://gateway.trycheatcode.com pnpm build && opennextjs-cloudflare upload"
+    "typecheck": "tsc -p tsconfig.json --noEmit"
   },
   "dependencies": {
     "@ai-sdk/react": "catalog:",

apps/web/package.json

@@ -18,6 +18,18 @@ const COMPOSIO_LIST_LIMIT = 500;
 // The SDK default base URL is already backend.composio.dev; pin it explicitly so a
 // future SDK default change can't silently repoint Workers at an unresolvable host.
 const COMPOSIO_BASE_URL = "https://backend.composio.dev";
+// Concrete toolkit versions pinned for deterministic discovery + execution. Without a
+// pin the SDK uses base version 00000000_00 (which can expose fewer actions than the
+// live toolkit), and "latest" would make manual tools.execute throw
+// ComposioToolVersionRequiredError. Fetched from GET /api/v3/toolkits/<slug> -> meta.version
+// on 2026-06-16; bump periodically. The LLM-supplied `version` in composio_execute still overrides.
+const COMPOSIO_TOOLKIT_VERSIONS: Record<string, string> = {
+  github: "20260501_01",
+  gmail: "20260615_00",
+  linear: "20260615_00",
+  notion: "20260615_00",
+  slack: "20260615_00",
+};
 const composioIntegrationNameSchema = z.enum(["github", "gmail", "slack", "notion", "linear"]);
 
 const requestContextReaderSchema = {
@@ -174,7 +186,12 @@ interface BoundedJson {
 // actually fires.
 async function createComposioToolClient(apiKey: string): Promise<ComposioToolClient> {
   const { Composio } = await import("@composio/core");
-  const composio = new Composio({ allowTracking: false, apiKey, baseURL: COMPOSIO_BASE_URL });
+  const composio = new Composio({
+    allowTracking: false,
+    apiKey,
+    baseURL: COMPOSIO_BASE_URL,
+    toolkitVersions: COMPOSIO_TOOLKIT_VERSIONS,
+  });
   return {
     execute: (slug, body) => composio.tools.execute(slug, body),
     getRawTools: (options) => composio.tools.getRawComposioTools(options),

apps/web/wrangler.jsonc

@@ -163,7 +163,7 @@ catalog:
   '@clerk/backend': 3.4.9
   '@clerk/nextjs': 7.3.4
   '@polar-sh/sdk': 0.46.4
-  '@composio/core': 0.8.1
+  '@composio/core': 0.10.0
   # ── Data ──
   drizzle-orm: 0.45.2
   pg: 8.21.0                                  # Required by Hyperdrive + Drizzle node-postgres setup (§7.3); omitted in the original catalog.
@@ -6421,6 +6421,35 @@ skill_invoke, skill_read_reference
 
 **Naming rules:** domain-first (LLM intent matches better), verb after, snake_case, ≤6 properties per tool (split if larger). Destructive or production-impacting actions require explicit first-class user commands and audit logging; V1 has no generic approve/reject tool gate.
 
+**Integration approach (deliberate — verified 2026-06-16):** The agent calls
+`@composio/core`'s low-level `tools.getRawComposioTools` (framework-agnostic
+discovery) and `tools.execute` directly, with **no Composio provider** set, and
+hand-wraps them in exactly two Mastra `createTool` meta-tools
+(`composio_list_tools` for runtime discovery, `composio_execute` for the
+action). Discovery projects each raw action to `{ slug, name, description,
+inputParameters, version, isDeprecated }` — the fields needed to then call
+`composio_execute` — rather than the default `OpenAIProvider` function envelope.
+Discovery passes the documented max `limit` (500; the API silently caps at ~20
+otherwise — github alone has 800+ actions) and accepts an optional `search`
+keyword so the model can narrow large toolkits server-side; the projected list is
+bounded into **valid JSON** by whole-tool count (never sliced mid-object). The
+client pins concrete per-toolkit `toolkitVersions` (fetched from
+`GET /api/v3/toolkits/<slug>` → `meta.version`) so discovery and `tools.execute`
+agree on one version and manual execute never throws `ComposioToolVersionRequiredError`;
+it also sets `baseURL` (= the SDK default `backend.composio.dev`, pinned) and
+`allowTracking: false` (no edge telemetry fetches). The LLM sees only these two
+tools — never N expanded per-action tools — so the tool list and token budget
+stay bounded. `@composio/core`
+(~1.2 MB) is dynamically `import()`-ed only when a tool fires, to stay under the
+Worker startup-CPU limit; per-request BYOK key, `userId`, and
+`connectedAccountId` are injected via Mastra `requestContext`. We deliberately
+do **not** use the framework providers `@composio/vercel` (emits a Vercel AI SDK
+`ToolSet`) or `@composio/mastra` (emits Mastra `createTool`s): both expand every
+action into its own tool, build the tool set eagerly, and capture a `Composio`
+instance at construction — which would regress the bounded tool surface, the
+lazy-import mitigation, and per-request BYOK/quota control. They are additive on
+top of `@composio/core`, not equivalent to it.
+
 **Composio execution contract:** `composio_list_tools` lists actions for an
 active user-connected integration. `composio_execute` resolves the user's
 `connectedAccountId` from `v2_user_integrations`, meters the call through the

packages/agent-core/src/mastra/tools/composio-tool.ts

@@ -4,6 +4,7 @@ Major SDK decisions verified before Week 1 implementation.
 
 | Date | Source | Version / Topic | Implementation implication | Plan status |
 |---|---|---|---|---|
+| 2026-06-16 | Context7 `/composiohq/composio`, npm registry (`@composio/vercel`, `@composio/mastra`), Vercel AI SDK v6 `tool()` spec, codebase `packages/agent-core/src/mastra/tools/composio-tool.ts` | `@composio/core` pin + the `@composio/vercel` "equivalence" claim | `@composio/core` is now pinned at **0.10.0** (was 0.8.1; `pnpm-workspace.yaml:17` was already correct, docs had drifted). `@composio/vercel` is a real, maintained, *separate* package (peer-deps `@composio/core` + `ai ^5\|\|^6`) whose `VercelProvider` wraps each action into a Vercel AI SDK `tool()` (`ToolSet`) and auto-executes via the SDK loop; `@composio/mastra` (`MastraProvider`) is the canonical Mastra provider. Both are **additive** (sit on top of `@composio/core`) and **not equivalent** to our usage: we call `@composio/core`'s `tools.get`/`tools.execute` directly with **no provider** (so the SDK's silent default `OpenAIProvider` is irrelevant), wrapped in two Mastra `createTool` meta-tools. The prior note that "`@composio/core` via Mastra is equivalent to `@composio/vercel` — no new dep" had the right conclusion (no new dep) but wrong framing (Mastra does not integrate Composio for us; "equivalent" is false). | KEEP the 2-meta-tool pattern; do **not** adopt `@composio/vercel`/`@composio/mastra` (they would expand to N eager tools, bind a `Composio` at construction, and defeat the lazy-import startup-CPU mitigation + per-request BYOK/quota control). plan.md §4 catalog + §25, CLAUDE.md, AGENTS.md updated 0.8.1→0.10.0. |
 | 2026-05-28 | Context7 `/vercel/ai`, Context7 `/browserbase/stagehand`, Firecrawl scrape of official Gemini pricing, npm registry | Google/Gemini BYOK runtime support | Current AI SDK docs use `@ai-sdk/google` and `createGoogle(...)` / `google("gemini-2.5-flash")`; Stagehand v3 docs support `model: "google/gemini-2.5-flash"` with `GOOGLE_GENERATIVE_AI_API_KEY`. npm reports latest stable `@ai-sdk/google@3.0.80`, depending on provider v3 utilities compatible with AI SDK v6. Official Gemini pricing lists `gemini-2.5-flash` paid-tier pricing at `$0.30 / MTok` input and `$2.50 / MTok` output. | Confirms the existing `google` BYOK provider should be wired into agent model selection, budget estimation, and Stagehand browser credentials instead of remaining validation-only; `plan.md` Section 4 and catalog updated. |
 | 2026-05-28 | Context7 `/vercel/ai`, Context7 `/mastra-ai/mastra`, npm registry | AI SDK v6 peer alignment with Mastra 1.35 | Current AI SDK docs still use `@ai-sdk/react` with `DefaultChatTransport` from `ai`, and Mastra docs require `toAISdkStream(..., { version: "v6" })` for AI SDK v6 streams. `@mastra/core@1.35.0` depends on `chat@^4.24.0`; current resolution `chat@4.29.0` peers `ai@^6.0.182`, and `@ai-sdk/react@3.0.184` depends on exactly `ai@6.0.182`. | Contradicted prior `ai@6.0.84` / `@ai-sdk/react@3.0.86` pins; `plan.md` Section 4 and the catalog were updated before continuing. |
 | 2026-05-26 | npm registry | `remend@0.3.2` unavailable; `remend@1.3.0` current | Lockfile sync failed because the plan-pinned `remend@0.3.2` no longer exists in the npm registry. `streamdown@2.5.0` declares `remend@1.3.0`, and `pnpm view remend version` reports `1.3.0`; Section 4 and the catalog were updated before implementation continued. | Contradicted plan; updated plan/catalog to `remend@1.3.0`. |