Generative UI (ggui)

Agents hosted on Guuey can reply with interactive UI — forms, dashboards, wizards, confirmation cards — instead of walls of text. That capability comes from ggui, an open, MCP-native generative-UI protocol. The agent describes what it needs in natural language; ggui compiles a typed component and the chat surface (Portal, the console’s playground, or an embedded widget) mounts it. When the user interacts, the agent receives typed events back.

Here is what that looks like on the live Trimly demo — asked for tomorrow’s open appointment times, the agent runs its ggui chain (visible in the chat rail) and renders a slot picker instead of listing times in prose:

How it reaches your agent

Guuey is MCP-server-agnostic. An agent’s definition lists whatever MCP servers it should use, and generative UI comes from the hosted ggui server at mcp.ggui.ai. The platform adds that server to every definition unless the definition declares ggui: false:

• Agents created in the console or in Studio start with Generative UI off: their definition declares ggui: false. Turn it on in the console’s Tools tab with the Generative UI for this agent switch, or under Superpowers in Studio.
• A new project from @guuey/create-agentic-app 0.34.0 and later declares it too, and so does the guuey.json of a console agent you move to code mode with guuey eject or guuey pull. Delete "ggui": false from agent.mcpServers, then run guuey deploy.
• An agent whose definition has no ggui entry keeps Generative UI on. That includes agents created before this change.
• Without the ggui server your agent is text-only.

Nothing about ggui is required: bring different MCP servers and your agent still deploys, streams, and persists exactly the same.

Where the protocol docs live

ggui is a separate open project with its own documentation at docs.ggui.ai. Go there for:

• How ggui works — the handshake → render → interact → consume walk-through
• Quickstart — wire ggui into any MCP-speaking agent, locally, in minutes
• MCP protocol reference — the wire surface
• Cookbook — worked patterns: forms, wizards, dashboards, auth-gated UI
• Self-hosting — run the whole protocol yourself with ggui serve, no account needed

The protocol’s SDKs are published on npm under the @ggui-ai/* scope — distinct from the @guuey/* platform tooling documented on this site.

The ggui docs are LLM-friendly the same way this site is — docs.ggui.ai/llms.txt is the machine-readable index.

guuey vs ggui

Guuey (this site) is the hosting platform — it runs your agent. ggui is the open protocol those agents can use for generative UI. They compose, but neither requires the other.