lazyplan (lpui) — v0.24.0
Plan work with your coding agent, in the terminal.
lazyplan is one shared plan for you and your agent. You get a fast keyboard screen. Your agent gets a simple command line. Plans, milestones, and tasks stay in one place instead of disappearing into chat. Read-only git and PR provenance shows where each one landed.
Install
pipx install lazyplan-tui
lpui --help
On Windows: pipx install --backend pip lazyplan-tui.
Prefer a system package or the one-line installer? See install options.
Start
cd ~/my-plan
lpui # first run detects agents and creates the plan store
lpui plan add --title "my-plan" --why "reason" --what "scope"
lpui
Working with a team? lpui setup --placement repo keeps the plan in the repo.
Want demo data first? Run lpui seed.
Why it feels different
- One source of truth. The plan you see is the plan your agent reads. No copy-pasting context between chats.
- Made for focus. Plans stay as one-line summaries until you open them. Detail is there when you need it.
- Yours to keep. Local-first by default. Export or import any time. No account, no cloud, no lock-in.
What you get
- A plan tree with progress at a glance, plus milestones and tasks underneath.
- A preview of the reason, the next tasks, and what done means.
- A read-only detail page for careful reading, with quick keys to edit and move work.
- One place your agent can update while you keep the big picture.
How it works
- Plans start as one-line summaries with progress. Open one to reveal milestones, then tasks.
- The right pane previews the selected row: why, what, next tasks, and acceptance progress.
- The bottom line shows the keys that work right now.
?opens help;copens the command palette. - Your agent writes through the same command line. The screen updates as it works.
Everyday commands
lpui list # plans and progress
lpui plan show --id 1 # why, what, criteria, milestones
lpui task move --id 1 --to doing # move work forward
lpui criterion tick --id 1 # tick the next acceptance item
lpui feed # recent activity
For your agent
The command line reads and writes the same plan, with JSON and clear exit codes:
lpui --actor helper task add --milestone 1 --title "Draft proposal"
lpui --actor helper list --json
Start with lpui brief to see the active task and the next step. After each
commit, link it and move the task. lpui audit --since 7.days --strict turns
the three accuracy metrics into a CI gate. lpui setup installs read-only
lifecycle hooks for detected agents; lpui setup --no-hooks removes them.
The first run installs the agent skill. lpui setup --placement repo generates the full contract in the repo.
Your data
Plans live in one local database: shared in your home by default, or inside a repo with lpui setup --placement repo. Back up with lpui export --format json; restore with lpui import --file. See data and backup.
Learn more
- Screenshots and quickstart
- Usage and CLI reference
- Setup walkthrough
- Contributing (main is protected; open a PR)
- Releases · Issues
MIT licensed. This repo plans itself: run lpui list.
1 maintainer
Metadata
1 maintainer
Release files for lazyplan-tui 0.24.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| lazyplan_tui-0.24.0.tar.gz | 229.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lazyplan_tui-0.24.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 394.0 kB
Release files / lazyplan_tui-0.24.0.tar.gz
| Download URL | lazyplan_tui-0.24.0.tar.gz |
|---|---|
| Size | 229.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e1a01ede776dcf309c5a21ee3262585c8d4464cc6229cb3580ce8ef1849bb47a
|
|
BLAKE2b-256 checksum How to use checksums |
54b3e468a8e94a45bac2c3145e2a927b009aedc22a6f0e395afdf15601357e5c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logRelease files / lazyplan_tui-0.24.0-py3-none-any.whl
| Download URL | lazyplan_tui-0.24.0-py3-none-any.whl |
|---|---|
| Size | 164.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33fdfb28f133b7cf2bcb73e4f5659b948f897c3af458104607e6b7b5a465c9bc
|
|
BLAKE2b-256 checksum How to use checksums |
9d81d9da66448391663a806ddfb8b55159ba746c07b8e8d8ea732dd2c9be101c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logSecurity for lazyplan-tui 0.24.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for lazyplan_tui-0.24.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
