Product / Dashboard & control
One dashboard.
Shaped by whatever you install.
The dashboard does not ship as a fixed set of screens. Every one of the 116 apps carries its own interface, and installing it adds that interface here — with the same navigation, the same permissions, and the same activity trail as everything else.
So the workspace ends up looking like the operation you actually run, rather than like a product someone else designed for an average customer.
It is the operating layer where agents, apps, permissions, and activity come together.
What you get
Every app brings its own panel
An app is not just tools for the agent. It ships an interface too, and it appears in your dashboard as soon as it is installed. Install a CRM and you get a CRM. Install billing and you get billing. The dashboard grows into whatever you are running.
Build a panel of your own
The same applies to apps you write. Build against the SDK, ship a panel with it, and it sits beside the first-party ones as an equal. There is no privileged set of built-in screens you cannot match.
Activity you can actually read
Follow what each agent is doing, inspect the tool calls it made and what came back, and see where it decided to wait. The record is written for a person to read, not only for a log aggregator.
Review before it matters
Name the actions that always need a person — anything that moves money, contacts a customer, or changes access. The agent stops and waits, and the record shows who let it through.
Boundaries you set per agent
Each agent gets its own goals, tools, and permissions. Scope is explicit rather than inherited, so one agent's reach is never the whole workspace's.
Cost in view, not in arrears
Model and tool spend is attributed per agent and per project while it happens, so an agent that starts costing more is something you notice rather than something you discover on an invoice.
Why this matters
Most agent tools give you a chat window and a log file. The work an agent does is real work — it touches customers, money, and systems — and it needs somewhere to be seen, approved, and corrected. That place should look like your business, not like a generic console.