Agent Mode · for SaaS builders
Asking is the new clicking.
Don’t leave your customer in the maze. Turn on your product’s Agent Mode. They ask, it happens, and generative UI draws a bespoke interface for every request.
Add Agent Mode → See a live agent work
7-day free trial
My bookings
Morning slots, drawn for your booking.
the same product, the same data. flip the switch, then watch Thursday’s booking move
The maze
Twenty-two clicks, or one question.
Dashboard Maze 😩
Agent Mode 😊
“Export Q3 invoices as CSV.”
✓ export card drawn · one click to downloadEvery question your dashboard cannot answer in one click is a ticket, a churn risk, or a conversation happening in someone else’s window. The maze is not a UX bug. It is what any deep product becomes. The fix is a second way in.
Why Guuey?
Because the machine under Agent Mode is one of one. Every answer is generative UI on the open GGUI protocol, an invalid interface never renders, and the runtime below does things most platforms cannot. The receipts:
A locked room.
One isolated runtime per app. Your data stays inside its walls, and heavy tools, running code, crunching files, transcribing audio, never leave it. Most platforms cannot host that.
Human-in-the-loop (HITL)
Nothing irreversible happens alone.
It acts as the signed-in customer, with exactly their permissions, nothing more. And anything destructive draws a confirmation surface first, held until a human clicks.
Drafts for Acme Inc, untouched for 30 days. Nothing is deleted until you decide.
It remembers.
Each customer’s context, kept.
Show more
Per-user memory is a durable home per customer. The agent keeps context between conversations: preferences, history, the small facts that make the tenth chat feel like the tenth. Signed-in customers only, guests stay anonymous, and nothing is used beyond answering that user.
It scales itself.
Launch-day traffic is our problem.
Show more
Each app runs on its own pods, and pods follow demand. A quiet Tuesday costs a quiet Tuesday. A launch spike scales out, then settles back down. Concurrency is enforced per plan, so the bill stays inside the plan.
The UI cache.
Interactive UI, served cheaper and faster.
Show more
The cache is for generative UI, never for answers. A surface the protocol has drawn before gets a deterministic content-hash key and renders again instantly, while the agent thinks fresh every time. The interface work is what gets cheaper and faster.
A/B, native.
Serve both, keep the winner.
Show more
Experiments live in the GGUI protocol itself. Serve two versions of a surface to real traffic, measure which one gets pressed, keep the winner. No third-party experiment tool bolted onto your agent.
You watch it work.
Every conversation, live in the console.
Show more
Sessions, Deployments, and Logs are console pages, not add-ons. Read any conversation, watch a deploy go healthy, tail the pod live. When something looks off, you see it in the same minute.
Every ask is a roadmap signal.
Sessions keep every conversation. The asks your customers type are the feature list they never put in a survey. The deflected tickets are the savings. This is the intelligence.
numbers illustrative. the feed is the console’s Sessions page, aggregated
A SKU, not a cost line.
A second way to use your entire product. Something your customers pay for, not something you absorb like a support tool.
Guuey’s side of it: plans from $49 a month per app, 7-day free trial. Pricing →
your pricing page, one row later
Super simple. Fully armed.
Adopting it is an afternoon in the console, not a quarter on your roadmap. Whatever your setup demands, one of the paths below fits it. Start now, this is the whole journey:
Define system prompt
Describe your product, the rules, the voice. If you can write an onboarding doc, you can brief an agent.
Acme helps teams ship invoices fast. Friendly, concise, never jargon
Choose the brain!
Claude out of the box. GPT and Gemini in the same dropdown. Swap without touching your page.
framework: claude-agent-sdk
Connect MCP tools.
One port. Every tool.
MCP is the port, and Guuey speaks it natively. Plug in whatever your product needs: connect a server you already run, hand yours to us, wrap your API, or build one inside the agent’s walls. Registries and scoped hosted state ride along. MCP docs →
You already run an MCP server, for Claude or anyone else. Point the agent at its URL. It stays on your infra, your deploys, untouched.
best for: teams already shipping MCP in prod
A full MCP server of your own, and we run it: scale-to-zero hosting, TLS, secrets handled. Ship the code, keep the ownership.
best for: a real server you want off your infra
Already have your own API? Then wrap it as MCP, easily. A thin adapter maps tools onto the endpoints you already have. No new service to own.
best for: the fastest path from API to agent
Any stdio server, living in the agent’s own pod. Zero hops, full sandbox. Real work: code, files, audio.
best for: heavy tools that never leave the sandbox
Connect an account once, and the MCP proxy does the rest: per-app grants, secrets injected at call time, OAuth tokens sealed at rest. The agent pod never holds a credential.
Custom theme
It dresses like your product.
Define your own custom theme on the Design page: colors, type, shape. The widget wears it, and so does every surface the agent draws. Generated UI arrives already dressed as your product.
Invoices, out the door.
Send, track, get paid.
the generated surfaces inherit the theme too
Preview your agent
Try every answer before a customer sees one. Change the brief, ask again, watch it improve.
Distribute
Three ways to ship it, and one will fit. Pick what fits today, switch any time.
Drop one line of HTML. The launcher appears in your corner, themed, ready to answer. The fastest route by far.
for your landing page or app, today
Integrate natively with the SDK. Mount the conversation anywhere in your UI, control the surface, keep your routing.
for a true in-app Agent Mode
Share the agent’s own link, or let customers find it in the Guuey app on web and mobile. Nothing to install in your product at all.
for starting before you touch your codebase
Custom domains, guest mode, metered per-app billing, and updates without a redeploy. Switch channels any time, the agent stays the agent.
The teardown: your product in Agent Mode, free.
Send us your product’s public MCP server. We record your product answering in working UI and send the video back.
one per company
The questions builders ask.
Can it take a wrong action?
It can only act through the tools your MCP server exposes, as the signed-in user, with their permissions. Anything destructive gets a confirm card before it happens.
Does it work with our auth?
Yes. Bring your own identity. Your login stays the login, and the agent sees exactly what that user is allowed to see.
What happens to our data?
It is used to answer your users and nothing else. The agent runs alone in its own runtime, one isolated pod per app, and every session inside runs in its own sandbox.
We do not have an MCP server.
Then yours is a thin translator over the API you already have, and Guuey hosts it. If you have one, you are a config file away.
What does it cost?
Plans from $49 a month per app after a 7-day free trial. Pricing →
Flip it on.
One script tag inside your product. Your MCP server, or ours to start. Agent Mode tonight.
The tour
From one line to their pocket — seven steps.
This is the exact walk our live demo gives every visitor, recreated here from the real Trimly fixtures. Drive the real one →
STEP 1 — ONE SCRIPT TAG
It starts with one line in your page.
Paste one script tag into the page you already have — that is the whole install. Trimly's booking agent shows up as a launcher in the corner, ready to talk. No SDK, no rebuild, no backend changes.
recreated from the live demo
STEP 2 — Guests just ask
No signup wall — visitors just ask.
The widget opens as a guest — no account, no form, no menu to learn. The first question gets typed the way people already type: like a text message. Trimly's agent takes it from there.
STEP 3 — A working card answers
The answer is an interface, not an essay.
Asked for Thursday times, the agent doesn't write back a wall of text. It draws the real slot picker — buttons, not paragraphs — ready to tap.
STEP 4 — Generated, and guaranteed
Drawn live by the agent — and an invalid interface can't render.
Every surface the agent draws is validated against the open GGUI protocol before it reaches the user. A well-formed slot picker renders; a hallucinated refund button is rejected at the checkpoint. It never ships.
render: slot_picker
date: 2026-08-23
slots: 4
STEP 5 — INSIDE YOUR PRODUCT
Your page, your brand — the agent lives inside it.
The same working card, embedded in Trimly's own site. The widget is the product's agent mode, not a third-party bubble — same domain, same chrome, same conversation.
STEP 6 — EVERY TURN, RICHER
Click it, and the agent finishes the job.
Pick a slot and it turns into a confirmed booking, right there on the canvas. No pasting details back into a chat box — every turn answers with a surface, not a transcript.
Trimly
Sunday, 2026-08-23
Select an available time slot with your preferred stylist
Booked — 2:00 pm with Dana · Thursday
this is a demo — nothing was really sent
STEP 7 — And in their pocket
The same agent rides along on mobile.
Every agent gets its page in the Guuey app — same conversation, same working UI. Android today, iOS on the way.
Sunday, 2026-08-23