Early preview — you found Guuey before launch · official launch soon

Hosting & runtime

read as .md

You bring a declarative agent definition — a system prompt, a model, the MCP servers your agent uses, and an optional tool allowlist. Guuey runs it. There is no SDK to import, no polling loop to write, no event handler to register: configuration and a prompt are the whole integration.

Everything lives in one file, guuey.json, validated the same way by guuey dev, guuey deploy, and the hosted runtime — one contract everywhere.

Isolated, long-running sandboxes

Each agent runs in its own long-running pod, sandboxed with gVisor — a much stronger isolation boundary than an ordinary shared container. Long-running means your agent isn’t rebuilt on every request; it stays warm across the turns of a conversation. When nobody is talking to it, it scales to zero, and the platform wakes it when the next conversation arrives.

The same isolation applies to MCP servers you host on Guuey. That matters most for compute workloads — code execution, binary tools like ffmpeg or pandoc, headless browser automation — the kind of thing most platforms can’t sandbox per tenant.

Streaming and history

Live responses stream over Server-Sent Events (SSE) directly from the pod running your agent — the client connects straight to the source, with no relay in between.

Conversation history is persisted automatically by the platform. Users can close the tab, come back later, and pick up the thread. You never build or operate a chat store.

Frameworks

Guuey is framework-adaptive: declare a framework in guuey.json, and the platform loads the matching runner, drives one turn per request, and streams the framework’s native events.

You declare	Runtime it drives
`claude-agent-sdk`	`@anthropic-ai/claude-agent-sdk`
`openai-agents-sdk`	`@openai/agents`
`google-adk`	`@google/adk`

For a no-code agent, that declaration plus your system prompt is everything — start from guuey config init or Studio. If you’d rather write framework-native code, deploy a code-mode project — a worker bundle or Dockerfile the CLI builds and ships. Scaffold a working code-mode project from a template:

npx @guuey/create-agentic-app my-agent

MCP servers: bring your own

Agents declare their MCP servers in guuey.json in three flavors:

hosted — Guuey runs the server for you.
colocated — the server runs alongside your agent, in the same sandbox.
external — any URL you point at.

The platform is MCP-server-agnostic: anything that speaks MCP works. The default server is mcp.ggui.ai — agents that keep it get generative UI out of the box, pushing real interactive interfaces to users instead of text-only replies. Generative UI, the protocol, and its SDKs are documented at docs.ggui.ai.

Local development

guuey dev --serve runs your agent locally under the same host harness used on Guuey pods, so your local loop matches production. When it works, ship it:

npm install -g @guuey/cli
guuey login
guuey deploy