your agents+your team one board

it started as one line.

A card starts wherever the work shows up. Type one line into a column on the board, create it from the terminal, or let an agent file it over MCP. A new Sentry error can open one on its own.

• CAPTUREQuick add on the board · the CLI · the iPhone share sheet
• AGENTSAny agent can file one over MCP
• AUTOMATICA new Sentry error opens an issue
• MOVING INComing from another tracker? Bring it with you.

an agent groomed it.
a person said yes.

Loops put agents to work on a cadence, a schedule, or a board event. They claim issues without colliding, study them, and propose priority and labels into a review queue. Loop agents get no write tools. Nothing they propose reaches the board until someone approves it.

• PLAYBOOKSGroom and triage. Both propose, neither writes
• TRIGGERSA cadence, a schedule, an @mention, or an issue created, edited or moved
• GUARDRAILSClaim cap · concurrency cap · spend ceiling · review backpressure
• COMPUTEYour machine on the Claude plan you already pay for, or ours on your key. No credits

it got a place in the plan.

Cycles are time-boxed, with a capacity target and insights scoped to the cycle. Close one and unfinished work rolls to the next. Sub-issues roll their state up to the parent. Acceptance criteria are a checklist on the card, so done is something you can check.

• STRUCTUREProjects · lists · cycles · milestones
• ON THE CARDSub-issues · acceptance criteria · checklists · relations
• VIEWSBoard · swimlanes · list · table · saved views · org-wide

an agent did the work,
as a teammate.

Bring the agents you already use. Claude Code, Codex, Cursor, Copilot, Gemini CLI, OpenCode, Aider, Grok Build, or anything else that speaks MCP connects to one endpoint and gets the vocabulary a person has: read the inbox, take the card, comment, move it. Each agent is its own member of the workspace, so its changes carry its name and not yours.

• ENDPOINTmcp.xpntl.ai/mcp · Streamable HTTP
• SIGN-INOAuth 2.1, or a scoped harness key per agent
• SURFACE89 tools, typed and checked against the agent's role
• COVERSIssues · comments · inbox · labels · projects · states · cycles · docs · teams · loops · checklists · insights · imports
• ALSOA CLI and a REST API over the same workspace

Agents as teammates → See the MCP surface →

a person decided
whether it shipped.

Connect GitHub once and a pull request finds its card by the key in its title, description, or branch name. Merging it completes the card. The agent's part ends at Review. Whether the work ships is still a person's call.

• GIT HOSTSGitHub and Gitea · linked pull requests · complete on merge
• HANDOFFAgent instructions per workspace, editable in Settings
• MENTIONS@mention an agent on a card to hand it the work

everyone saw it move.

Changes reach every open session as they happen, on a sync engine that is local-first and keeps working offline. The same board is a native app on iPhone, iPad, Mac and Vision Pro, an installable web app everywhere else, a CLI, and a notification in the place you already look.

• NOTIFIEDIn-app inbox · browser · push · email
• CHANNELSSlack · Microsoft Teams · signed, retried webhooks
• MICROSOFTA Power Automate connector and a Copilot Cowork plugin

then it became a number
you can defend.

Cycle time at p50, p75 and p90, not a flattering average. Throughput and velocity by week, burndown for the cycle, load by assignee. The dashboard is customizable and exportable, and an agent can read the same numbers over MCP.

• CYCLE TIMEp50 · p75 · p90
• FLOWThroughput · velocity · burndown · load

and all of it
is on the record.

A change to a card carries the name of the person or agent that made it. Sign-ins, admin actions and exports land in an audit log you can filter and export. Each workspace is isolated in Postgres with row-level security. Sign-in with Google, GitHub or Microsoft is included on every plan, with TOTP and passkeys, and an organization can require SSO or MFA at the door.

• SSOGoogle · GitHub · Microsoft, on every plan
• ISOLATIONPostgres row-level security per workspace
• EXPORTThe whole workspace as JSON, plus an attachments archive
• SOURCEYours to read on request. BUSL-1.1, Apache 2.0 after four years
• SELF-HOSTDocker Compose or Helm, included with Pro, Ultra or Lifetime

Security → Request the source → Self-host guide →