The Wire · Showcase
VERCEL FUNCTIONS SHIPS WEBSOCKET NATIVE SUPPORT, EVE FIXES CRITICAL DEV PATH BLOCKERS
By RepoJournal · Filed · About Vercel
Vercel Functions now handles WebSocket connections natively in public beta, while Eve's dev runtime rebuilds and MCP connection flows are finally working end-to-end.
WebSocket support across Vercel Functions is now documented and shipping [1][2], complete with guidance on Socket.IO transports and Next.js experiments. Developers can stop reaching for polling workarounds and drop the myth that streaming requires Edge runtime. On the Eve side, three critical dev-facing fixes landed: MCP connections are now usable in local development [3], the dev-only rebuild route is wired up, and HITL approval resume handling works correctly with text shortcuts [4]. GitHub channel webhooks forwarded through Vercel Connect no longer require standard headers [5], inferring event type from payload shape instead. Eve's agent info probe now retries transient 5xx failures [6], stopping false negatives during dev worker reloads. CORS handling across Eve channels now defaults permissive with proper preflight support [7]. AI SDK v7 picked up Sentry observability [8], JSON response handlers now respect size limits [9], and patch releases flowed through @ai-sdk/rsc, @ai-sdk/svelte, and the full Node.js builder stack [10][11][12][13][14][15][16][17].
Action items
- → Review and merge manifest-ci-gate PR (#103) so WebSocket docs PR (#102) retargets automatically to main vercel/vercel-plugin [immediate]
- → Test WebSocket + MCP dev flows end-to-end before deploying to staging vercel/eve [plan]
- → Update internal docs: streaming no longer requires Edge runtime, poll the WebSocket guide instead vercel/vercel-plugin [monitor]
References
- [1] feat(vercel-functions): WebSocket guidance + SSE/streaming clarification ↗ vercel/vercel-plugin
- [2] feat(vercel-functions): WebSocket guidance + SSE/streaming docs (#102) vercel/vercel-plugin
- [3] fix(eve): make MCP connections usable in dev ↗ vercel/eve
- [4] fix(eve): HITL approvals - repair resume contract ↗ vercel/eve
- [5] fix(eve): github channel - infer headerless webhooks ↗ vercel/eve
- [6] fix(eve): retry transient agent info probes ↗ vercel/eve
- [7] fix(eve): channels - default permissive CORS ↗ vercel/eve
- [8] docs: add Sentry observability guide ↗ vercel/ai
- [9] fix(provider-utils): limit JSON response handler reads ↗ vercel/ai
- [10] Version Packages ↗ vercel/ai
- [11] @ai-sdk/[email protected] ↗ vercel/ai
- [12] @ai-sdk/[email protected] ↗ vercel/ai
- [13] @vercel/[email protected] ↗ vercel/vercel
- [14] @vercel/[email protected] ↗ vercel/vercel
- [15] @vercel/[email protected] ↗ vercel/vercel
- [16] @vercel/[email protected] ↗ vercel/vercel
- [17] @vercel/[email protected] ↗ vercel/vercel
FAQ
- What changed in Vercel on June 28, 2026?
- Vercel Functions now handles WebSocket connections natively in public beta, while Eve's dev runtime rebuilds and MCP connection flows are finally working end-to-end.
- What should Vercel teams do about it?
- Review and merge manifest-ci-gate PR (#103) so WebSocket docs PR (#102) retargets automatically to main • Test WebSocket + MCP dev flows end-to-end before deploying to staging • Update internal docs: streaming no longer requires Edge runtime, poll the WebSocket guide instead
- Which Vercel repositories shipped on June 28, 2026?
- vercel/vercel-plugin, vercel/eve, vercel/ai, vercel/vercel