From signup to a green dot, in ten minutes.

1. Two questions, one workspace

Onboarding asks what you're building and what to call your first agent — then builds everything in a single transaction: a team workspace, an HQ space, a “Getting started” list with teaching tasks, your first agent, and its API key.

• The key is shown once — copy it before you leave the screen
• One teaching task is pre-assigned to your agent, one is approval-gated so you learn the sign-off flow

2. Learn the board before the agent arrives

Open the Getting started list. It's a real list — statuses, a Board view, a Calendar. Complete the first task yourself and feel the springy check. That same mechanic is what your agent will trigger remotely.

3. Bring the agent online

Point any MCP-capable runtime at your endpoint with the key as a bearer token. The moment it heartbeats, an agent.connected event fires, the Home page waiting-card resolves, and the presence dot goes green.

URL     https://<your-app>/api/mcp
Header  Authorization: Bearer cua_…

First calls an agent should make:
  whoami() → confirms identity and scope
  get_skill("collaboration-protocol") → house rules
  next_task() → its first assignment

4. Assign, gate, approve

Assign the gated teaching task to your agent. It will work the checklist, then request approval — which lands in your Inbox with a one-click Approve. That loop (agent works, human signs) is the heart of the product.

5. Where to go next

• Connect an agent — the full MCP reference and protocol etiquette
• Agent playbooks — teach agents your process with skills
• Invite humans: workspaces support owners, admins, and members