Stop drowning in AI .md files.
A free, open-source CLI and MCP server for the planning docs your AI agents write. It versions every revision, links each plan to the issue it belongs to, and tells you when one has gone stale.
pip install flanner- MIT
- licensed
- 100%
- local, no account
- MCP
- Claude Code + Codex
Everything you need to manage AI plan files
Built for AI-assisted development with Claude Code, Codex, and any MCP client
Your agent files plans itself
MCP tools for Claude Code and Codex, plus a guard hook, managed CLAUDE.md/AGENTS.md blocks and a skill. The agent routes plans through flanner without being reminded, and a raw write into the plan directory is refused.
You find out when a plan goes stale
Every plan carries a status backed by evidence: dead references, commits since it was written, age. When one stops being true, flanner tells you which part gave way.
Every revision is kept
Each edit becomes a new version with full history. Nothing is overwritten, so you can read what a plan said before the agent changed its mind, and diff any two versions.
Plans stay attached to the work
Link a plan to a Linear or Jira issue and it stops being a loose file. Titles and states refresh from the tracker, so the connection survives the sprint it was made in.
Nothing lands in git by accident
Plans live in .plans/ and are kept out of commits automatically. You decide if and when any of them becomes part of the repository.
It all stays on your machine
A local SQLite catalog and markdown files in your own directory. No account, no upload, no network. Flanner Mesh, the team tier, is on the roadmap, and will still store none of it.
All of it through three surfaces that share one catalog: a CLI, an MCP server your agent drives, and a local web UI for reading and reviewing. See the command reference.
Every plan has a half-life
Flanner tracks the evidence behind every plan: what it cites, what changed since it was written, and whether those references still exist. As the code moves on, the status moves with it. When a plan goes stale, flanner can tell you why.
The decay is not a hunch. It is measured.
of repository docs carry outdated code references at some point in their history.
Empirical Software Engineering, 2023 ↗of repos have stale references inside their AI context files like CLAUDE.md and AGENTS.md.
Context Rot, 2026 ↗Check your own repo in one command.
pip install flanner && flanner freshnessHow flanner works
From init to a fully versioned plan history, in five steps
Initialize
Run 'flanner init' to set up the database, create .plans directory, and auto-register with Claude Code
Create Plans
Ask Claude to create plan files through MCP or Manually create and attach files to your local projects
Track Versions
Every update creates a new version with complete history and metadata preserved
Manage & View
Use the web UI or CLI to browse plans, view history, and manage your projects
Collaborate
Link plans to Linear and Jira issues. Team sync, on the roadmap, sends them directly to your teammates' devices rather than to us
Built for how developers actually work
Whether you're solo or on a team, flanner adapts to your workflow
Solo Developers
Keep your architecture decisions and planning organized with AI assistance from Claude
Development Teams
Share plan files, track who made changes, and maintain consistent documentation across the team
AI-First Workflows
Let Claude Code manage your planning documents while maintaining version control and audit trails
Project Documentation
Store RFCs, technical specs, and architecture decisions with automatic versioning
Open Source Projects
Manage project roadmaps and feature planning with git-ignored local plan files
Remote Teams
Asynchronous collaboration with web dashboard access and clear ownership tracking
Keep plans tied to the work
Connect flanner to your issue tracker. Linear syncs live; more are on the way.
Linear
live status syncTwo-way sync over the Linear API. Plans update automatically as their linked issues move through your workflow.
Jira
supported · linksLink any plan to a Jira issue for traceability. Link-based today, without live status sync.
More coming
GitHub Issues, Notion, and more integrations are on the way.
Flanner Mesh
The local tool is free and open source today. Team sync is on the roadmap, and it keeps the same shape: plans travel directly between your team's authorized devices, with no VPN and no ports to open, and flanner does not store your plan content. Join the waitlist to hear first.
Leave your email and you'll get exactly one message the day it ships. No spam.
Ready to Get Started?
Install Flanner, connect it to Claude Code or Codex, and start managing your plan files with confidence. Free and open source.