Flux · 
Flux is a completely open, hackable, unopinionated task management engine.
Flux is your ultimate task management sidekick – a lightning-fast Kanban board that lets humans, AI agents, and automations team up to crush chaos. With built-in MCP (Model Context Protocol) integration, your LLMs can jump in and run the show: creating tasks, updating statuses, and keeping everything in sync. No more rigid workflows or SaaS lock-in – just pure, flexible productivity magic! ✨
Why settle for boring task trackers when you can enter the Flux Zone? Inspired by the wild energy of a flux capacitor (hello, Back to the Future fans!), this open-source gem decouples tasks from execution, making it the perfect playground for developers, teams, and AI enthusiasts. Ready to go viral? Star this repo and let's make task management fun again! ⭐
Why Flux? Because Chaos is So Last Year
Ever felt like your projects are a tangled mess of tools, bots, and half-baked ideas? Flux fixes that by being:
- Execution-Agnostic: Tasks live here, but how they get done? That's up to you – manual, API, webhooks, or let Claude/GPT take the wheel.
- AI-Powered Awesomeness: Hook up your LLMs via MCP and watch them automate the mundane. "Hey AI, create a task for fixing that bug!" – Done. 🤖
- Simple & Speedy: Single JSON file, drag-and-drop UI, git-native sync. No bloat, just flow.
Flux isn't just another Kanban board – it's the open-source engine for the future of work. Developers love it because it's hackable, extensible, and screams "build on me!" If you're tinkering with AI agents or just need a better way to organize, this is your ticket to productivity paradise.
Sample workflow
Features
-
Multi-Project Kanban Boards: Juggle epics, tasks, and dependencies like a pro.
-
Task Dependencies: See what's blocked at a glance – no more surprises!
-
MCP Integration: Let LLMs list, create, update, or delete tasks programmatically.
-
Real-Time Updates: SSE keeps everyone in sync – web UI, APIs, and beyond.
-
Webhooks Galore: Integrate with Slack, GitHub, CI/CD – trigger actions on task changes.
-
API-First Design: Full REST endpoints for ultimate control.
-
Git-Native Sync:
flux push/flux pullsyncs viaflux-databranch. -
CLI-First: Full CLI with MCP parity (
flux ready,flux task, etc.) -
Agent Memory: Task comments for persistent context across sessions
-
Priority System: P0/P1/P2 priorities for agent task ordering
-
Blob Storage: Attach files (images, docs, logs) to tasks via CLI, API, or MCP.
Quick Start: Up and Running in a Flux Second ⚡
# CLI only (npm)
npm install -g flux-tasks
# Full stack with Web UI (Docker)
curl -fsSL https://raw.githubusercontent.com/sirsjg/flux/main/scripts/quickstart.sh | bash # macOS/Linux
irm https://raw.githubusercontent.com/sirsjg/flux/main/scripts/quickstart.ps1 | iex # Windows
This will start both the web UI (http://localhost:3000) and the MCP server. Press Ctrl+C to stop the MCP server when you're done.
# Claude Code
claude mcp add flux -- docker exec -i flux-web bun packages/mcp/dist/index.js
# Codex
codex mcp add flux -- docker exec -i flux-web bun packages/mcp/dist/index.js
Let your agent know!
cat << 'EOF' >> AGENTS.md
---
You are an autonomous agent using Flux for task management.
RULES:
- All work MUST belong to exactly one project_id.
- You MUST NOT guess or invent a project_id.
- You MUST NOT switch projects without explicit instruction.
STARTUP (MANDATORY):
1. List projects.
2. Select or create ONE project.
3. Confirm the active project_id before any work.
EXECUTION:
- Include project_id in EVERY Flux call.
- Track all work as tasks.
- Update task status as work progresses.
- Close tasks immediately when complete.
- Comment on tasks where appropriate.
CONTEXT LOSS:
- If unsure of project_id, STOP.
- Re-list projects and tasks.
- Ask the user if ambiguity remains.
FORBIDDEN:
- Working without a confirmed project_id.
- Mixing tasks across projects.
- Relying on memory outside Flux.