praxec/cpm-planner

cpm-planner is a Critical Path Method (CPM) planner for agent work, exposed as an
MCP server. You submit a task graph and it computes the schedule: earliest and
latest start and finish, slack, the critical path and the bottleneck tasks that
gate completion. It then leases **lock-aware cohorts** of ready deliverables with
disjoint file sets, so several workers can run in parallel without colliding.
Plans can live in the repository as plan-as-code files with forkable, comparable
variants; read-only tools lint, level against resource capacities and run Monte
Carlo risk; earned-value tools track PV, EV, AC, SPI and CPI against a frozen
baseline; and an optional AI review proposes verified schedule improvements. Any
MCP client (Claude Code, Cursor, VS Code, Codex, a custom orchestrator, or a
praxec workflow) drives it over stdio. It is a
standalone tool with no dependency on praxec.
Contents
- Install
- Prebuilt binary (recommended)
- Pin a version
- npm
- From source
- Docker
- Verify the install
- Quickstart: plan as code
- Quickstart: earned value
- Use with AI agents
- MCP tools
- Plan-as-code workflow
- Plan review (optional)
- Use as a library
- Praxec
- Environment variables
- Documentation
- Contributing
- License
Install
Prebuilt binary (recommended)
Prebuilt packages are published for Linux, macOS and Windows on x86_64 and ARM64.
The installers resolve your OS and CPU and download the matching archive. They
**verify its SHA-256 against the release's checksums.sha256 before installing**,
then atomically replace the binary in a user-local directory. A checksum mismatch
aborts with a non-zero exit and installs nothing. Re-running the installer upgrades
in place.
The installer prints the absolute path it installed to. Use that path when you
register the server with a GUI client.
Installer details: inspecting the script, PATH, upgrades and direct downloads
If you would rather read the script before running it, download, inspect, then run
(see Pin a version for ):
**PATH.** If the install directory is not on your PATH, the installer prints the
exact line to add. Pass --add-to-path (-AddToPath on Windows) to have it do that
for you, user-level only and never with sudo.
On Linux and macOS it appends the line only if it is not already there, to:
- ~/.zshrc for zsh;
- ~/.bash_profile if it exists, else ~/.bashrc, for bash;
- ~/.profile for other shells.
For fish it prints fish_add_path for you to run instead of writing a file.
**Downloads.** The installers only accept https:// download URLs.
**Upgrades.** After upgrading, restart your MCP client so it launches the new
binary. On Windows the old exe is renamed to cpm-planner.exe.old and removed on
the next run.
**Direct downloads.** You can also download an archive yourself and check it
against checksums.sha256; a machine-readable release-manifest.json is published
too. All assets are at .
| Platform | Asset |
|----------|-------|
| Linux x86_64 | cpm-planner-x86_64-unknown-linux-gnu.tar.gz |
| Linux ARM64 | cpm-planner-aarch64-unknown-linux-gnu.tar.gz |
| macOS x86_64 | cpm-planner-x86_64-apple-darwin.tar.gz |
| macOS Apple Silicon | cpm-planner-aarch64-apple-darwin.tar.gz |
| Windows x86_64 | cpm-planner-x86_64-pc-windows-msvc.zip |
| Windows ARM64 | cpm-planner-aarch64-pc-windows-msvc.zip |
Pin a version
In the commands in this README, is a release tag such as v0.2.0. Pick
one from the releases page.
npm
With Node 18 or later, install the cpm-planner command from npm:
The package is a small launcher. It downloads the release binary for your
platform, verifies its checksum and caches it, during install or, where npm
skips install scripts, on first run. The package
version is the release version, so npm install -g @matthew-cochran/cpm@0.2.0
pins one. To run it without installing, use npx -y @matthew-cochran/cpm.
For details and environment variables, see npm/README.md.
From source
Build and install a tagged release with Cargo (Rust 1.99 or newer):
The crates.io listing lags behind the GitHub releases until the next
cargo publish, so cargo install cpm-planner does not give you the current
version yet. Install from the tag as above.
Docker
-i keeps stdin open for the stdio transport.
The image sets CPM_PLANNER_DB=/data/cpm-planner.db and declares /data as a
volume owned by the unprivileged app user, so a named volume persists plan state
across runs. For a bind mount (-v "$PWD:/data"), run as yourself so the directory
is writable: --user "$(id -u):$(id -g)". Pass -e CPM_PLANNER_DB=... only to