About mdflow

mdflow is a Git-native control plane for repeatable agent work. Define a job as a Markdown file, keep it in a project's flows/ directory, and run it on an installed agent CLI. Frontmatter supplies configuration; the body supplies the prompt. The flow stays readable, reviewable in a pull request, and reusable by a teammate or coding agent.

When to use it

Use mdflow for work you expect to repeat: code review, release notes, issue triage, and other jobs that benefit from shared instructions and declared inputs. Workflows execute only through the local CLI; the website serves read-only documentation and source facts. Your local environment supplies the engine, credentials, files, and permissions. The default engine is pi; supported engine names are claude, copilot, codex, gemini, droid, opencode, pi, cursor-agent, agy, grok, kimi. An engine must be installed and configured before it can run a flow.

Inspect, evaluate, then improve

Start with md doctor --json for a static readiness report. Inspect an individual flow with md explain <flow.md> --json, noting that imports may resolve. Colocated behavioral evals can check a flow's declared behavior, but a suite's presence is not proof that it passes. Evolution records feedback and creates private proposals; changing the source requires a separate, explicit apply decision.

Open source and project ownership

The project lives at johnlindquist/mdflow and is distributed under the MIT license. The CLI is free; engine subscriptions or provider usage can cost money. See pricing and costs, the documentation, and contact and security reporting. The repository is the authoritative place to inspect the implementation, release history, license, and contribution guidance.