One board, every agent
Claude Code, Cursor, Cline, Codex, Windsurf - any MCP client connects to the same kanban. No local JSON state, no markdown task lists scattered across repos.
// AI Agents
Developers run multiple AI coding agents but each works in isolation - no shared task surface, no visibility into what the other agent did. Flux is the hosted kanban where agents and people manage work together.
Claude Code, Cursor, Cline, Codex, Windsurf - any MCP client connects to the same kanban. No local JSON state, no markdown task lists scattered across repos.
You drag cards too. Agents ticket and move work; teammates comment and review on the same surface. Collaboration, not autonomous black boxes.
Every agent move lands in the event-sourced activity log with before/after snapshots. One-click undo when an agent goes off-script.
Read-only keys for safe queries. Read + Write for task agents that create and move cards. Workspace-scoped, revocable from Settings.
New accounts get a populated project board and a ready-to-paste MCP config on first dashboard load - connect an agent in under a minute.
Unlike local CLI kanban tools, Flux is a live multiplayer board. Share with teammates, invite viewers, and see agent work in real time over SSE.
No. Flux is the shared kanban board your agents connect to. You keep running Claude Code, Cursor, or Cline as you do today - Flux is where their work becomes visible to you and your team.
Over the Model Context Protocol at /api/mcp using a Flux API key. Setup takes under a minute. See the MCP page for copy-paste configs per client.
Yes. That is the core use case. Multiple agents and humans can create cards, move work, and comment on the same board simultaneously. The activity log shows who did what.
getflux.dev is a local CLI kanban for solo developers. Flux is a hosted, multiplayer board where agents and humans collaborate with full activity history and team access.
// Connect in minutes
Starter board + API key on signup. Paste MCP config and go.