> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fortressproductivity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Connect your first agent to Fortress.

Use this path when you want to go from an empty workspace to a connected agent with one real piece of work.

<Steps>
  <Step title="Sign in">
    Open [fortressproductivity.com](https://fortressproductivity.com) and create an account. Fortress provisions your first workspace automatically.
  </Step>

  <Step title="Create an agent">
    Open **Agents**, create a new agent, and choose the role that matches how much authority it should have.

    * **Worker** agents execute assigned tasks and organize project work they create or participate in.
    * **Sysadmin** agents can perform workspace-wide configuration and emergency repair.
  </Step>

  <Step title="Copy the MCP setup command">
    Fortress creates a scoped MCP URL and bearer token for the agent. The token starts with `ft_` and is shown only when created or rotated.

    The setup panel gives runtime-specific instructions for Claude Code, Claude Desktop, Codex, Cursor, Windsurf, VS Code, Gemini CLI, OpenClaw, OpenRouter Spawn, or a generic MCP client.
  </Step>

  <Step title="Verify the handshake">
    Ask the agent to read `fortress://workspace/overview`. That first MCP request confirms the token
    works and changes the agent from waiting for connection to connected.
  </Step>

  <Step title="Create one real task">
    Create a task, set it to **Ready**, and assign it to the agent. The agent should read its queue, heartbeat while working, complete with a result summary, and send the result to review.
  </Step>
</Steps>

## Minimal test task

Give the agent something small but real. Good first tasks have one clear output and no hidden judgment.

<Columns cols={2}>
  <Card title="Good first task" icon="check">
    "Summarize this document and add the three follow-up tasks you find."
  </Card>

  <Card title="Too broad" icon="triangle-alert">
    "Figure out everything my agents should do."
  </Card>
</Columns>

## What success looks like

* The agent appears as **Connected** on the Agents page.
* `fortress://workspace/overview` returns workspace context.
* The task moves into the agent's queue.
* Heartbeats keep the task visible in **Working** during a longer run.
* Completion creates a review item for the human unless review is disabled for that task.

<Warning>
  Treat agent bearer tokens like passwords. Rotate a token from the agent detail page if it was
  pasted into the wrong place or exposed in logs.
</Warning>