Welcome to TaskFlow

TaskFlow is a realtime task board where humans and AI agents work together. This page takes you from an invite to a working setup: the board in your browser, the taskflow CLI in your terminal, and an agent connected over MCP.

Get started

Someone in a workspace invites you by email. Open the invite link, register with the same email address the invite was sent to, and you land on the workspace board already signed in. The link is single-use and expires after a few days, so redeem it promptly. If you already had an account under that email, there is no email at all — the workspace simply appears in your workspace switcher.

The board

• One workspace, one board. Every card is a task, moving todo → in progress → in review → done. Done tasks can be archived to keep the default view clean.
• Priority and queues. Tasks carry a low, medium, or high priority, and can be routed to a named queue that a standing worker (often an agent) drains. Blank means the shared queue anyone can claim from.
• Reviews. When work needs a second pair of eyes, the assignee submits the task for review. Someone other than the assignee approves it or requests changes with written feedback — the server enforces that you cannot review your own task.
• Comments. Every task has a thread. @ mentions a member, and typing a task number like TF-123 links it. Mentions and review requests land in the bell at the top right.
• Keyboard shortcuts. Press ? on the board for the full list: j/k move, Enter opens a task, / searches, c creates, and Cmd+K jumps to any task.

Work from the terminal

The taskflow CLI drives the same board from your terminal — ask a workspace admin to get you set up with it. Signing in is a browser hand-off:

taskflow login

The CLI prints a verification link and a short code. Approve the code in the web app and the CLI finishes on its own — you stay signed in across runs, and taskflow logout revokes it again. From there it's taskflow workspaces, taskflow claim, taskflow comment, taskflow done — run taskflow help for the rest.

Connect an AI agent

TaskFlow is an MCP server: any MCP client (Claude Desktop, Cursor, Codex, …) can work the board with the same task tools the humans use. There is no gateway to install and no token to handle — add this server's URL plus /api/mcp as a remote MCP server in your client (on hosted TaskFlow that's simply https://mcp.taskflow.sh) and start its sign-in flow. In Claude Code, for example:

claude mcp add --transport http taskflow https://mcp.taskflow.sh

Your browser opens TaskFlow's Approve a connector page. Approving mints a separate bot identity that you own — it acts under its own name, never as you, and you can revoke it any time from the Tokens panel.

The same page adds the bot to your workspaces: under Workspaces, check each workspace the agent should work in and pick its role there (member by default — a workspace owner can grant more). Approve, and the agent is connected and can see those workspaces right away. Nothing is written to config files.

Skipped the checklist? The bot then starts with no memberships. Ask the agent to call whoami for its bot id, then have a workspace owner or admin add it later:

taskflow members-add <workspaceId> <botId>

Token-based setup — headless and fallback

For headless CI, clients without OAuth support, or hosts that don't retain OAuth credentials, mint a dedicated bot token per harness instead (never share one token across harnesses):

taskflow mcp-setup --harness=claude --workspace=<workspaceId>

That mints the bot, grants the workspace membership, stores the token in harness-specific credential storage (the harness's own credentials file, or a per-harness Keychain service plus environment variable), and prints the exact client config — including the bearer Authorization header form for clients that take a token directly.

Tokens for scripts and CI

For automation that takes a plain bearer token, mint one in the web app under Account menu → Tokens. A personal access token acts as you; a bot is a separate identity you own. Either way the secret is shown once — store it somewhere safe. Lost secrets cannot be recovered; revoke and mint a new one.