Console tour¶
The Console is the web interface of the Console API: everything on it is a route in the route reference, and what you can change depends on your role (viewer, operator or admin). A command palette jumps to any team or agent.
Navigation¶
| Page | What you do there |
|---|---|
| Teams | See teams and their state; create one from a template with a repository and a home; open a team for its roles, links, budget, documents, MCP servers, task box and runs; archive it. |
| Agents | Read an agent and its versions; edit its prompt, tools, egress and documents as a new version; make an old version current. Admin. |
| Templates | Read and version team templates. Admin. |
| Runs | Every run, filtered by state or team. A run shows its tasks per role, cost, delivery (branch and pull request), the trace link and its conversation; answer a waiting question, follow up or cancel. |
| Spend | Spend per team and per day against budgets. |
| Environments | Sandbox profiles, images and checkpoints. Admin to change. |
| MCP servers | Platform and team MCP servers and their credential status. |
| Skills | Platform skills and a team's own. |
| Integrations | Connect Mattermost, Slack, GitHub, Linear and Jira, test them, see whether the gateway applied the change, and link teams. Admin. |
| Settings | Users, authentication, import of definitions, API tokens and Onboard your agent. |
First login¶
There is no default account. An admin is created on the database with just console-admin create; the admin
invites everyone else from Settings, Users, which gives a one-time setup link. See Console API.
Working from the Console only¶
A team made with no chat home takes work from the task box on its page: type a task, follow the conversation on its run, answer when the run asks. Runs has the details.