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/mcpYour client signs in with OAuth. No key to paste. Claude Code, Cursor, VS Code
you
What can I start on the progress feature?
agent
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.
What can start now is computed.
The order comes back in waves. Everything in a wave runs at once.
Wave 11 agent
- task_xvt1667f2eactivereadycompletedProgress schema and the types every screen reads
Wave 23 agents
- task_bt7fsv9t8xactiveblocked · dependencyactivereadyProgress in the weekly digest
- task_mqvj2k0z2jactiveblocked · dependencyactivereadyProgress bar on the dashboard
- task_wbpe91gx01activeblocked · dependencyactivereadyBackfill progress for existing accounts
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
task_07np4tg1qqactivereadyFix the failing deploy
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
https://flow.ttoss.dev/mcpclaude mcp add --transport http flow https://flow.ttoss.dev/mcp{
"mcpServers": {
"flow": { "url": "https://flow.ttoss.dev/mcp" }
}
}{
"servers": {
"flow": { "type": "http", "url": "https://flow.ttoss.dev/mcp" }
}
}
Terezinha is Flow’s bot on Discord. Flow is a ttoss product.


