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_427710rp22activereadyProgress schema and the types every screen readsfrees 3
task_qwre53g75qactiveblocked · dependencyProgress bar on the dashboard
task_s45n7fvx2ractiveblocked · dependencyProgress in the weekly digest
task_psak7624zhactiveblocked · 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_427710rp22activereadycompletedProgress schema and the types every screen reads
Wave 23 agents
- task_psak7624zhactiveblocked · dependencyactivereadyBackfill progress for existing accounts
- task_qwre53g75qactiveblocked · dependencyactivereadyProgress bar on the dashboard
- task_s45n7fvx2ractiveblocked · dependencyactivereadyProgress in the weekly digest
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_0nn08p750gactivereadyFix the failing deploy
Connect it.
One endpoint, 35 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.


