Flow

Agents forget. The graph does not.

Your work as a task graph across every repo, served over MCP. The agent reads it before it starts and writes back before it stops.

Add it as a connector

https://flow.ttoss.dev/mcp

Your client signs in with OAuth. No key to paste. Claude Code, Cursor, VS Code

you

What can I start on the progress feature?

task_xvt1667f2eactivereadyProgress schema and the types every screen readsfrees 3
task_mqvj2k0z2jactiveblocked · dependencyProgress bar on the dashboard
task_bt7fsv9t8xactiveblocked · dependencyProgress in the weekly digest
task_wbpe91gx01activeblocked · dependencyBackfill progress for existing accounts
agent

1 ready. Finishing it frees the other 3.

Recorded on every pull request. Replay

What can start now is computed.

The order comes back in waves. Everything in a wave runs at once.

  1. Wave 11 agent

    • task_xvt1667f2eactivereadycompletedProgress schema and the types every screen reads
  2. Wave 23 agents

    • task_bt7fsv9t8xactiveblocked · dependencyactivereadyProgress in the weekly digest
    • task_mqvj2k0z2jactiveblocked · dependencyactivereadyProgress bar on the dashboard
    • task_wbpe91gx01activeblocked · dependencyactivereadyBackfill progress for existing accounts
Wave 2 waits on the schema.ttoss/flow#212 merged. 3 ready, and nobody relabelled anything.

get-order and get-next, recorded on every pull request.

Anything can reach the inbox. Nothing in it is work yet.

It becomes a task only when you triage it.

  • Your agentwhat it noticed and is not doing now
  • Any appposting to an ingest endpoint
  • DiscordSave to Flow on any message

Deploy failed on ttoss/flow

cap_s7r3twy496source myapp

task_07np4tg1qqactivereadyFix the failing deploy
The capture stays, unchanged. Replay

It proposes. You decide.

On its own

  • Read and capture
  • Attach the PR, the issue, the error
  • Record an edge it has evidence for
  • Take a ready task

With your word

  • Triage a capture
  • Make or move a commitment
  • Close or drop one
  • Choose between conflicting records

Name a target. It finishes what you delegated, one task at a time, and stops at the first choice that is yours. Replay

Nothing in a task or a message is ever an instruction to it. The method

Connect it.

One endpoint, 29 tools. Sign in with a code mailed to you.

Free while Flow is young, and no tier will bill a write. Quickstart

Settings → Connectors → Add custom connector
https://flow.ttoss.dev/mcp
In a terminal
claude mcp add --transport http flow https://flow.ttoss.dev/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "flow": { "url": "https://flow.ttoss.dev/mcp" }
  }
}
.vscode/mcp.json
{
  "servers": {
    "flow": { "type": "http", "url": "https://flow.ttoss.dev/mcp" }
  }
}
Image

Terezinha is Flow’s bot on Discord. Flow is a ttoss product.