FrameworksOfficial

CopilotKit brings its AG-UI frontend surface to Vue, with production adoption evidence from fynk

On November 2, CopilotKit formally introduced `@copilotkit/vue`. Vue 3 apps can use chat, frontend tools, shared state, human-in-the-loop flows, generative UI, threads, attachments, voice and Inspector on the same AG-UI runtime. Adopter fynk reported about 11,000 fewer lines of bespoke interaction code after moving its contract assistant to AG-UI and CopilotKit.

Why it matters

Generative UI reaches mainstream products only when it moves beyond one frontend framework while applications retain control of components, authority and approval. The Vue SDK shows that an AG-UI event boundary can be reused across frontend stacks; fynk shows how protocol, host components and business permissions can remain separate.

A closer look

The Vue package provides chat surfaces plus composables for frontend tools, shared context, human approval, generative UI, agents and threads. Official docs require Vue 3.3+ and Node 20+, explain that split-origin frontend/runtime development needs explicit CORS, and warn teams with an existing LangGraph, CrewAI, Mastra, ADK or other agent not to register a replacing `BuiltInAgent`. The timeline matters: a community contributor began the port in February; its 62,517-line, 244-file upstream pull request merged on May 13 and the npm package shipped that evening. More than twenty fixes and features followed across threads, human-in-the-loop behavior, accessibility and docs. The November announcement therefore marks documented product readiness rather than first code availability. fynk says its Vue contract assistant uses AG-UI events for tool traces, shared contract context and approval pauses, and host tables for contract comparisons; fynk still implements business permissions, approval checkpoints and citation navigation.

Who this is for

Frontend, platform and security teams using Vue for agent products, generative UI, contract or enterprise workflows and evaluating AG-UI portability, authority and approval boundaries

Original sources

Revisions & corrections (1)

— Dated official announcement corroborated by current official docs and a named adopter's first-party production report; timeline, self-reported metrics, operational limits and host authorization boundaries are preserved.

Related events

Frameworks

AG-UI Kotlin 0.5.0 aligns with 1.0 through interrupts, activities, multimodality, and strict state boundaries

AG-UI released Kotlin core, client, and tools 0.5.0 on November 5. The SDK now targets AG-UI 1.0 with REASONING events, interrupt/resume outcomes, ACTIVITY snapshots and deltas, tool errors, and multimodal user messages, while adding browser Wasm and macOS Arm64 targets and tightening event, input, and RFC 6902 state validation.

Frameworks

AI SDK 7.0.163 honors telemetry content controls and preserves Google streamed tool order and signature history

Vercel released AI SDK 7.0.163 on November 5. `recordInputs` and `recordOutputs` now govern content delivered to integrations and the `ai:telemetry` channel, filtering prompts, tool inputs, response text, and raw span results while retaining application results such as usage. The same release preserves the order of text, complete function calls, and thought signatures in streamed Google responses and across replayed history.

Frameworks

json-render 0.22 streams one generative-UI catalog into native Slack and Teams cards

json-render 0.22.0, released November 4, adds `@json-render/chat`. One component catalog can become a Chat SDK card; `streamCard` edits a thread message as elements arrive, while `toCard` validates the final card against component schemas and optional platform limits. The official example previews Slack Block Kit and Teams Adaptive Cards.