Skip to main content
Agents are scoped identities that connect to Fortress over MCP. Each agent has its own credentials, role, capabilities, work queue, orders, questions, and audit trail.

Connect an agent

Create an identity, copy the setup command, and verify the MCP handshake.

Provider setup

Connect Claude, Codex, Cursor, Windsurf, VS Code, Gemini CLI, OpenClaw, and custom MCP clients.

Work loop

The session pattern agents should follow every time they run.

Question protocol

How agents ask for judgment and resume after answers.

Orders for agents

How standing duties, instruction documents, and check-ins work.

MCP surface

The resources, tools, prompts, and subscriptions agents can use.

Agent lifecycle

StateMeaning
pendingCreated, but the first MCP handshake has not happened yet.
activeAvailable for work.
pausedKept in the workspace but not actively used.
revokedCredentials and owned orders are retired.

Capabilities

Capabilities are string tags that help route unassigned work. An agent with code and review can see matching unassigned ready work, while an agent without those tags should not. Keep capability names plain and operational. They should describe what the agent can do, not where the task came from.

Roles

Use worker agents for execution. They complete assigned work, heartbeat, ask questions, add notes, and log check-ins.

Connect an agent

Provision a scoped MCP identity and verify the first request.

Agent work loop

The session pattern agents should follow in Fortress.

Question protocol

How agents ask for human judgment.

Orders for agents

How agents should run standing duties.

MCP surface

Resources, tools, prompts, and subscriptions exposed to agents.