Use the Console

The Console, at platform.guuey.com, is where you operate the agents you host on Guuey. Whether an agent was built in Studio or deployed from code with the CLI, it shows up here — with its deployments, sessions, logs, tools, design, users, domains, and billing.

Sign in with your Guuey account — the same one you use in Studio and Portal. A scope switcher in the top bar moves you between your personal space and any workspace you’re a member of; everything below (agents, registries, usage, billing, settings) is read in the active scope.

The map

The main sidebar has six sections:

Section	What’s there
Home	Your agents as cards, with a jump into each
Agents	The full agent list and the create form — see Agents & deployments
MCP Registries	Workspace MCP server catalog, your hosted servers, and hosting billing — see Tools & MCP
Usage	Generations used this month, per agent — see Billing & workspaces
Billing	The wallet view: every subscription in the scope, plus Stripe invoices — see Billing & workspaces
Settings	Your profile, API keys, and workspace management — see Billing & workspaces

External links at the bottom of the sidebar open Studio and these docs.

Inside an agent

Opening an agent swaps the sidebar for that agent’s own navigation, grouped the way you work:

• Agent — Overview and Playground → Agents & deployments
• Configure — Behavior, Tools, Design, Users → Agents & deployments, Tools & MCP, Design & distribution
• Distribute — Distribution, Embed, Domains → Design & distribution
• Monitor — Sessions, Deployments, Logs → Agents & deployments
• General — Billing and Agent Settings → Billing & workspaces, Agents & deployments

A dropdown above the navigation switches between your agents without going back to the dashboard.

Console, Studio, and the CLI

Three doors onto the same platform:

• Studio is where no-code agents are authored — instructions, model, capabilities. For an agent built in Studio, the Console’s Behavior tab sends you back to Studio to edit it; the Console still owns everything operational (deployments, sessions, billing, domains, design).
• The CLI is the code path: guuey deploy ships an agent defined in guuey.json (see Agents as code). The Console’s Redeploy button re-runs your most recent deploy; new configuration still comes from the CLI or Studio.
• The Console is the shared operations surface for both.

Truthful by policy

Where a control isn’t built yet, the Console says so: sections that aren’t live render a labelled “coming soon” panel — often naming the CLI command or file that does the job today — rather than a form that silently does nothing. Editable controls are wired; where one saves a field the runtime doesn’t read yet (the Generated UI preset picker, the Adapters labels), the panel says so right beside it.

Platform health

Platform health lives at status.guuey.com — live checks on the Console, the CLI API, agent endpoints, and the MCP gateway. If the Console misbehaves, look there first.