AGENT UI WIDGETS
Agent UI Widgets — Give Your AI Agents a Real Interface, Not a Text Dump
2026 shipped the agent-UI layer: MCP Apps, Google's A2UI, and a wave of "shadcn-for-agents" component kits. They all attack the same gap — the layer above chat, where you see what the agent is doing instead of reading what it says. VibeFuse goes one layer further: widgets are not rendered by the agent — the whole desktop is a widget canvas the agents live in. Free, Windows 10+.
The 2026 agent-UI stack, mapped
Every serious agent in 2026 runs in a loop — call tools, read results, iterate. A raw text stream is a terrible interface for that loop, and the ecosystem finally agrees. Four layers shipped within eight months:
| Layer | What shipped | When | License / access |
|---|---|---|---|
| Component kits ("shadcn-for-agents") | NexUI — 90+ agentic components for Vercel AI SDK v6 (tool renderers, thinking indicators, agent shells). Brainless — rebuilds the Claude Code, Codex, and Grok interfaces as copy-paste React. 21st.dev agent-elements — 26 primitives incl. Bash/Edit/Search/Todo tool cards. | H1–mid 2026 | MIT / BSD, copy-paste — you own the code |
| Flutter agent_kit 0.1.4 | ToolCallCard, ToolCallFeed, ThinkingBubble, ReasoningTrace, CitationChip, PlanProgress — backend-agnostic, streaming-safe, zero provider-SDK dependencies. Companion mcp_client package landed September 2026. |
Jun 2026 (v0.1.4 Jun 10) | BSD-3 |
| Google A2UI (Agent-to-UI) | Agents stream declarative UI as JSON Lines; the client renders native widgets per platform (Flutter via GenUI SDK, Web Components, Angular). CopilotKit renders A2UI through its AG-UI protocol. Format v0.8. | Public Dec 15, 2025 | Apache 2.0 |
| MCP Apps (SEP-1865) | The first official MCP spec extension: MCP servers attach sandboxed HTML widgets to tool results, rendered inline in Claude, ChatGPT, and Microsoft 365 Copilot. Co-authored by Anthropic and OpenAI maintainers; 10 launch partners incl. Figma, Slack, Canva, Amplitude. | Merged Jan 28, 2026 | Open spec |
| Harnesses as UI platforms | DeepSeek Harness — everything-is-a-plugin, including the UI itself: the Web UI, chat nodes, and third-party UI plugins all mount as swappable Cordis plugins. CopilotKit ships generative-UI primitives for in-app copilots. | Aug 2026 | MIT (DeepSeek Harness, 212K+ stars) |
The pattern behind all four: an agent's loop produces structure — tool calls, diffs, plans, citations — and the UI should render that structure, not narrate it. Even the component kits say it plainly: the chat-UI market is crowded; the layer above chat is wide open.
What VibeFuse adds: widgets ARE the agent UI
Everything in the table above assumes a chat window that agent output gets rendered into. VibeFuse is the first ever free widget-based AI harness, and it inverts the assumption: there is no chat window to render into — the desktop itself is a canvas of widgets, and the agents are widgets on it.
Agents as live widgets
Claude Code, Codex, Gemini CLI, Cursor Agent, Qwen — real PTY terminals tiled beside browser, files, video, and notes widgets. The agent loop is visible, interruptible, and rearrangeable at all times.
Vibe Agent + Jarvis
The first-party assistant tiles the canvas, types into terminals, and calls MCP tools — the agent rearranging your UI is the generative-UI loop, not a mockup of it.
Marketplace-sourced UI
An open-source marketplace where users make money selling widgets, skills, and styling packs — install community widgets into the canvas with one click, with revenue share for creators via Stripe Connect payouts.
widget:// iframes
Marketplace widgets render as sandboxed iframes addressed by widget:// — local/offline processing that works in any app, not just inside VibeFuse.
MCP wired in
Google Workspace & Drive, GitHub, Copilot, Discord, Linear, and custom stdio MCP servers — the same protocol the new widget standards ride on.
$0 harness fee
VibeFuse itself is free with a complimentary VF- license, Windows 10+ x64. Pay agent vendors if you want; pay nothing for the harness or the canvas.
The difference in one line: chat-SDK kits give you components to build an agent app; VibeFuse is the app — a Windows-native desktop where agents, tools, and marketplace widgets already live together. The full harness picture is in the AI agent harness guide; the catalog of built-in surfaces is on the AI widgets page.
Widget harness vs chat SDK vs declarative protocol
| Question | VibeFuse (widget harness) | Chat SDK kits (NexUI, agent-elements, CopilotKit) | Declarative protocols (MCP Apps, A2UI) |
|---|---|---|---|
| Where it runs | Windows desktop, local/offline | Your own web app (React/Flutter) | Inside third-party hosts (Claude, ChatGPT, Copilot) or any A2UI client |
| Who owns the surface | You do — the canvas is the product | You do — but you build and host it | The host does — sandboxed iframes, host-defined limits |
| What the agent renders | It lives in the UI: PTYs, browser, files, Jarvis-arranged layouts | Tool cards, thinking traces, generative-UI parts | Sandboxed HTML (MCP Apps) or JSONL-described native widgets (A2UI) |
| Monetization | Marketplace: sell widgets, skills, styling packs — Stripe Connect revenue share | None built in — you monetize your own product | None — spec-level only |
| Offline | Yes — local processing by design | Depends on your stack | No — hosts fetch and render remotely |
Where the 2026 stack still wins
Full credit where it is due — the web-first layers solve problems VibeFuse deliberately does not touch:
Reach
MCP Apps and A2UI put widgets inside Claude, ChatGPT, and Copilot — audiences no desktop app can reach. If your users live in those hosts, the specs are the right call.
Embedding
The shadcn-for-agents kits are the correct choice for React teams shipping agents inside their own product — copy-paste code you own, no runtime lock-in.
Trust boundaries
A2UI's declarative-JSON approach and MCP Apps' sandboxed iframes render untrusted agent UI safely across org boundaries — a problem a local desktop harness simply does not have.
Not on VibeFuse: rendering widgets inside third-party chat hosts. VibeFuse owns its desktop canvas instead — which is exactly why its widgets can be local, offline, and monetizable.
- ✓ Widgets ARE the UI
- ✓ Marketplace payouts
- ✓ MCP tools included
- ✓ Local + offline
- ✓ Windows 10+
Explore VibeFuse & harness guides
- Harness Guide
- Free Coding Tools
- AI Coding Agent Desktop
- Free Voice Transcription
- Free Text to Speech
- VibeFuse Product
- Widget Marketplace
- Download Free
- VibeFuse Docs
- Shareable AI Widgets
- Shareable AI Skills
- MCP Tools
- AI Agent Harness
- Harness Engineering
- HyperFrames Video
- Skill Seekers
- Sell AI Skills
- AI Skills Marketplace Compared
- Cursor Alternative
- Local Whisper + Piper
- Custom AI Dashboard
- Community Hub
Agent UI widgets FAQ
What are agent UI widgets?
Components that visualize what an AI agent is doing instead of narrating it as text: tool-call cards, thinking indicators, plan-progress timelines, citation chips, diffs, and approval prompts. 2026 standardized this layer with MCP Apps, Google A2UI, and a wave of shadcn-for-agents component kits.
What is MCP Apps?
The first official extension to the Model Context Protocol (SEP-1865, merged January 2026, co-authored by Anthropic and OpenAI maintainers). MCP servers attach sandboxed HTML widgets to tool results, which Claude, ChatGPT, and Microsoft 365 Copilot render inline in the chat.
What is Google A2UI?
Agent-to-UI — an open Apache 2.0 protocol (public December 2025) where agents stream declarative UI as JSON Lines and clients render native widgets per platform: Flutter via the GenUI SDK, Web Components, or Angular. CopilotKit renders A2UI surfaces through its AG-UI protocol.
Are there component libraries for building agent UIs?
Yes — the "shadcn-for-agents" wave: NexUI (90+ agentic components for Vercel AI SDK v6), Brainless (Claude Code, Codex, and Grok interfaces as copy-paste React), 21st.dev agent-elements (26 primitives with tool cards), and Flutter agent_kit (ToolCallCard, ThinkingBubble, CitationChip, PlanProgress).
How is VibeFuse different from these agent UI kits?
The kits give you components to build an agent app yourself. VibeFuse is the app: a free Windows desktop harness where widgets ARE the agent UI — live agent terminals, browser, files, and marketplace widgets on one canvas, installable in one click, local and offline.
Can I make money selling agent widgets?
Yes. VibeFuse runs an open-source marketplace where users make money selling widgets, skills, and styling packs, with revenue share for creators and Stripe Connect payouts — a monetization layer none of the chat-SDK kits or UI protocols include.
Does agent UI require the cloud?
Not in VibeFuse: widgets process locally and work offline on Windows. MCP Apps and A2UI widgets usually render inside cloud-hosted chat clients, which is the reach-versus-control trade-off between the two approaches.