Documentation is a pull system. You go find what you need. A plugin is a push system. Knowledge finds you at the moment you need it. The difference is the same gap that separates polling an API every five seconds and subscribing to a webhook.

Every system for getting information to a consumer falls into one of two categories: pull or push. In a pull system, the consumer initiates the request. They know what they need, they know where it lives, and they go get it. In a push system, the producer initiates the delivery. The consumer declares what they care about, and relevant information arrives when it becomes available.

The Vercel Plugin for Claude Code now ships a hybrid prompt matching engine that combines exact phrase matching with full-text lexical search, synonym expansion, and suffix stemming. The result: skills are injected when the developer means something, not just when they say the exact magic words.

Three variations targeting different reader motivations. All technically grounded in Workflow DevKit documentation and following Vercel blog editorial conventions.

Format: Deep-dive Primary keyword: durable AI streaming

Three variations, each covering a different angle. All draw from the same product (Workflow DevKit) and the same proof points, but target different reader motivations.

Format: Deep-dive (1200-1500 words) Primary keyword: durable AI streaming

Key differences between Claude Code and Cursor hook formats:

The Vercel Sandbox API rejects resources: { vcpus: 1 } with a 400 error, but multiple documentation pages show or imply 1 vCPU as a valid configuration. The actual minimum is 2 vCPUs (even numbers only).

This matters for I/O-bound workloads. We measured CPU utilization inside OpenClaw sandboxes over a 2-hour live test: <2% CPU even at 162 msgs/hr sustained. A 1 vCPU / 2 GB tier would halve memory costs, which are 97-99% of total sandbox cost for this workload.

OpenClaw sandboxes on Vercel needed a manually-configured AI_GATEWAY_API_KEY environment variable to authenticate with Vercel's AI Gateway for LLM inference. This was a deployment friction point — every new deployment or team member needed the key configured.

Replaced the static API key with Vercel's OIDC (OpenID Connect) token federation. The dashboard's Vercel Functions automatically receive an OIDC JWT that proves they're running on Vercel infrastructure. AI Gateway accepts this JWT as a bearer token — no static key needed.

Generated: 2026-03-02 Source: GPT-5.2 Pro (via Oracle) + web research (March 2026) Tools compared: Claude Code, Cursor, Codex CLI, OpenCode, Gemini CLI, Windsurf, VS Code / Copilot, Aider

Legend: ✅ full support | 🟡 partial/limited | ❌ no support

Reviewed: 2026-03-02 Reviewer: GPT-5.2 Pro (via Oracle) + Claude Opus 4.6 Scope: Full project review against Claude Code's plugin system for cross-harness viability

When publishing Next.js apps via the v0 Platform API using chats.init({ type: "files" }), the preview (demo-*.vusercontent.net) does not execute API routes, Server Actions, or any server-side code. Every request — including POST /api/my-route — returns the page HTML instead.

This makes it impossible to build interactive demos that use workflow, database connections, or any backend logic when publishing via the Platform API.

The same app connected via chats.init({ type: "repo" }) gets a real Vercel Sandbox where API routes work, workflows execute, and server-side code runs as expected.