PMO CLI
Work PMO from your terminal. Find your next task, record progress and close it with evidence, without opening the board.
The PMO CLI is pmo, a single program you install on your own computer. It works the same records as the PMO board, through the PMO server, so everything you do from the terminal appears on the board at once and is recorded under your name. People use it to stay in their editor; AI sessions and scripts use it because every command is one line they can run and check.
# Sign in once, with your Cross account$ pmo login# Pick up the next task that is yours$ pmo next --mine --claim$ pmo start example-project-12$ pmo note example-project-12 "Sample file loads; three columns need renaming"# Close it with what proves it is done$ pmo done example-project-12 --evidence "Merged: https://github.com/example-org/example-repo/pull/88"
Install
irm https://github.com/cross-systems/pmo-cli/releases/latest/download/install.ps1 | iexThen run pmo login. Releases are published at github.com/cross-systems/pmo-cli; run the same line again to update.
Get started
Install on Windows
Install on a Mac or Linux
Sign in
Everyday work
What you can do with it
| Area | For example | Reference |
|---|---|---|
| Your tasks | Ask for the next task, claim it, note progress, block it, close it with evidence | Tasks |
| Features | Write what "finished" means, move a feature through its stages, mark it planned or taken on later | Features |
| Modules and projects | Create them, record where each stands for the client report, set what waits on what | Modules, Projects |
| Clients | Record what the client owes you, dated updates, report editions and private portal links | Clients and client reports |
| Planning | The portfolio at a glance, engagements, milestones, decisions and time left | Engagements and planning |
| You | Who you are signed in as, and what your role lets you change | Account and reports |
Every command is in the command reference, generated from the program itself so it cannot drift from it.
For AI sessions and scripts
An AI session runs the same commands with its own key, tied to the person who runs it. Every change it makes records both names. It can only close work with --evidence, and closing a feature's last task needs --criteria-met, which confirms every point of the feature's definition of finished. Add --json to any command for machine-readable output, and rely on the exit codes: pmo next exits with code 1 when there is nothing left, so a loop can stop on it.
Learn more
- How the PMO CLI works: what it is, what it is not, and how it reaches the server.
- Troubleshooting: every message, what it means and what to do.