Start Here · 01.06
Workspace Tour: From Agent Fleet to Operating Apps
A hands-on map of the Agentis workspace: Home, Agents, Apps, Brain, Assets, history, and the controls that connect them.
The product surfaces you actually use
The documentation explains the platform's concepts; the workspace is where an operator applies them. The current application has dedicated routes for Home, Agents, Apps, Brain, Assets, History, Chat, and Workspaces. Global controls provide search, notifications, a chat panel, connections, and profile/settings access.
This matters because Agentis is not only a workflow editor. The UI deliberately joins a living agent organization, the products it operates, the knowledge it compounds, and the evidence left by each run. Use the navigation to change context; use the page controls to do work in that context.
http://127.0.0.1:5173/ on 30 July 2026. Screens below show that workspace, so names, counts, and statuses are illustrative rather than product defaults.Explore the Project 3gT7 workspace
Choose any tab above. The tabbed view is enhanced with JavaScript, while every capture remains readable if scripts are unavailable.
What each surface is for
| Surface | Use it when you need to… | Typical next action |
|---|---|---|
| Home | Orient yourself in the workspace authority canvas and start a conversation with the orchestrator. | Open the live workspace, select a visible resource, or ask the chat scope for a plan. |
| Agents | See the organizational shape, runtime status, roles, domains, and each agent's private Brain. | Filter the fleet, open an agent, create a specialist, or import an existing agent/package. |
| Apps | Operate products rather than isolated graphs: interface, logic, data, and memory in one place. | Open an App, create a new App, inspect extensions, or promote a standalone workflow. |
| Brain | Inspect and manage workspace or personal knowledge, skills, examples, learning, and their map. | Search the Brain, switch its scope, or configure it. |
| Assets & History | Find produced files and verify what a run or conversation actually did. | Open an artifact, inspect run activity, or follow a conversation back to its source. |
A reliable first tour
- Start on Home to establish which workspace and ambient context you are operating in.
- Open Agents and find the orchestrator, its managers, and any specialists. Use the Fleet/Brain switch deliberately: the former is about ownership and routing; the latter is about each agent's mind.
- Open Apps to identify the product that owns a workflow. Treat a workflow as the logic inside an App wherever an App owner exists.
- Use Brain before rebuilding knowledge that may already be grounded, then use History to judge whether a previous run merely completed or actually accomplished its outcome.
- Use chat, command search, and notifications as cross-cutting controls when you know what you want but not the exact page that owns it.
Continue
Describe intent, build, validate, dry-run, run, and deliver — the paved road every Agentis workflow follows, walked end to end with a real example.
The Agentis thesis: identity, memory, and skills are durable platform state you own; the model executing a turn is a swappable, disposable tenant.