Learn
Learn TaskFlow
How the board works, how to drive it from a terminal or an AI agent, and how it's built under the hood.
Getting started
Already signed in? The in-product tour walks you from an invite to a working setup — the board, the CLI, and an agent connected over MCP — in one pass. Take the tour.
The board
One board per workspace. Tasks move todo → in progress →
in review → done, carrying a priority and an optional queue a
standing worker — often an agent — drains. A review gate keeps the assignee from
approving their own work, the same rule whether a human or an agent is driving.
See the full board tour.
Work from the terminal
The taskflow CLI drives the same board from your terminal. Signing in is a
browser hand-off:
taskflow login
The CLI prints a verification link and a short code; approve it in the web app and the
CLI finishes on its own. From there it's taskflow workspaces,
taskflow claim, taskflow comment, taskflow done —
run taskflow help for the rest, or browse
every command. See Get TaskFlow
for the install command.
Connect an AI agent over MCP
TaskFlow is an MCP server: any MCP client (Claude, Codex, Cursor, …) can work the board
with the same task tools a person uses, acting under its own bot identity that you own
and can revoke — never as you. There is no gateway to install and no token to handle;
point the client at https://mcp.taskflow.sh and sign in with OAuth. In
Claude Code:
claude mcp add --transport http taskflow https://mcp.taskflow.sh
Authenticate at the client's OAuth prompt and your browser opens TaskFlow's consent card. Approving mints a dedicated bot for the agent — and right on the card you pick the workspaces the bot joins, with a role in each (member by default). Approve and the agent is connected and can see those workspaces; nothing is stored in config files.
Running headless CI, a client without OAuth support, or a host that loses OAuth
credentials?
The full setup guide covers the
token-based fallback — taskflow mcp-setup per-harness bot tokens, a bearer
Authorization header, Keychain/env storage — or browse
every tool before you connect.
Architecture
TaskFlow runs as one deployable unit by design: a single server binary with SQLite on one
volume, the web app baked into the same container image, and bring-your-own SMTP (or
Resend) for outbound email — nothing else to stand up alongside it. TaskFlow is offered
today as a hosted service at taskflow.sh; there's no self-serve download or
public source repository.