The console¶
The console is the web application everything else on this site is configured through. This page is the map: what each area is for, and which page explains it properly.
If you are looking for one screen, the fastest route is the "?" in a page's header — it replays that page's walkthrough, and a page whose header carries no "?" has no walkthrough to replay.
The dashboard¶
The landing page is an arrangeable grid of widgets, and it is the answer to "what is happening" without opening five pages.
Thirty-five cards exist. You will not see all of them: a card is gated on the permission its data needs, so a widget you may not read is never mounted and its queries are never issued. An empty band disappears with its heading rather than sitting there empty.
They arrive grouped into bands:
| Band | Answers |
|---|---|
| (untitled, at the top) | The summary the rest of the page is the detail of |
| Deployment | Only for a deployment admin — platform totals, health, busiest tenants, ratings |
| Attention | What is waiting: approvals, recent failures, budget headroom, MCP health, stale knowledge |
| Usage | Runs, outcomes, surfaces, latency, spend, model mix, version comparison |
| People | Members, active users, ratings, who is doing what |
| Sandboxes | Capacity, live sessions, policy |
| Workspace | Yours: your agents, your conversations, your activity, what was shared with you |
Rearranging it¶
Drag a card, resize it, hide one. The arrangement is yours — scoped to you and the organization you are in, not to the organization — so changing it changes nobody else's page.
Save an arrangement as a named preset to keep more than one and switch between them. A duplicate name is refused rather than silently overwriting the snapshot you meant to keep.
The gate runs last, on whatever it is handed
A saved arrangement can reorder and hide, but it cannot reveal. Permission filtering runs after the layout is resolved, whether the layout came from the default or from your own saved one.
Chat¶
Where you talk to a published agent. The picker chooses which agent answers, and the run behaves exactly as it would in Slack or behind the API — same budget, same approval gate, same audit trail, because every surface goes through one runner.
Three things in the composer worth knowing.
Your own accounts. An agent bound to each person's own account on a service speaks to it as you. The chat's controls list which of the agent's services need an account of yours and whether each is ready, with a connect button that opens the provider's consent in a new tab. Ask before connecting and the agent says it cannot reach the service - and a card under the answer offers the same button, so the fix is one click from the refusal.
Attachments are parsed and handed to that conversation only; they are not added to a knowledge collection. See File processing.
Slash commands expand to a prompt before the message is sent. The built-in ones ship with the product; you can write your own under Settings → Slash commands, and hide any built-in you never use. They are yours, not the organization's.
What each area is for¶
| Area | It holds | Read |
|---|---|---|
| Agents | The catalog, the Builder, versions, sharing, testing, activity | Your first agent |
| Chat | Talking to a published agent | Surfaces |
| Knowledge | Collections, documents, sync sources, ingestion settings | File processing |
| Skills | Written procedures an agent loads on demand | Skills |
| Context | Standing knowledge bound to many agents | Context files |
| Routines | Schedules and event triggers | Triggers |
| Runs | What ran, what it cost, what it touched, whether it failed | Governance |
| Sandboxes / Workspaces | Isolated file-and-shell sessions an agent worked in | The sandbox |
| MCP servers | Connections to external tools, personal and organization-wide | MCP |
| Channels | Slack, Telegram and Mattermost bots, widgets, hosted pages | Surfaces |
| Vault | Credentials, sealed per organization | Secrets |
| Organizations | Members, roles, invitations | Permissions |
| Settings | Providers, ingestion defaults, notifications, your own profile | Configuration |
| Admin | The deployment itself: users, tenants, system, deployment settings | The deployment |
When a page looks empty¶
An empty state and a failed request look the same. Every page here fans out to several queries and renders "nothing yet" when one of them fails.
So before concluding a collection is empty or an agent has no runs, check the network tab. This is the single most common way a real problem gets read as a quiet one.
Recap¶
- The dashboard is thirty-five permission-gated widgets you arrange yourself, saved per person and per organization.
- A saved arrangement can hide and reorder but never reveal — the gate runs last.
- Chat, Slack and the API are the same runner, so what you see in the console is what a customer gets.
- Slash commands are yours, built-in ones included, and you can hide the ones you do not use.
- A page showing "nothing yet" may be a failed request, not an empty resource.