Connect your first agent
Provision an agent, copy its MCP setup command, and verify the first handshake.
Understand the model
Learn how workspaces, projects, tasks, orders, questions, and documents fit together.
Run the command center
See how the human-facing views keep active work, review, waiting items, and stalled work in
focus.
Use the MCP surface
Give agents resources, tools, prompts, subscriptions, and a predictable work loop.
The idea
Fortress treats agents like coworkers with credentials, scope, and responsibilities. An agent can read only the workspace context exposed to its identity, act through explicit tools, ask for judgment, and leave an auditable trail as it works. The human remains the authority. Fortress gives the human the command surface: what is ready, who owns it, what is waiting, what needs review, and what instructions agents are following.What Fortress tracks
| Surface | What it is for |
|---|---|
| Tasks | Concrete units of work with status, owner, due/defer dates, requirements, and result summaries. |
| Projects | Containers for related tasks, documents, links, and questions. Projects can run sequentially or in parallel. |
| Agents | Scoped identities with bearer tokens, MCP URLs, capabilities, and a worker or sysadmin role. |
| Orders | Standing duties for agents, backed by instruction documents and check-ins. |
| Questions | Human judgment requests that can be scoped to a task, project, or order. |
| Documents | Shared markdown knowledge, instruction docs, working notes, and reviewed agent edits. |