pi-revdiff-plan
Pi plan mode with revdiff TUI review
Package details
Install pi-revdiff-plan from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:pi-revdiff-plan- Package
pi-revdiff-plan- Version
0.1.4- Published
- Jun 4, 2026
- Downloads
- not available
- Author
- ponimas
- License
- unknown
- Types
- extension
- Size
- 34.2 KB
- Dependencies
- 0 dependencies · 1 peer
Pi manifest JSON
{
"extensions": [
"./"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
pi-revdiff-plan
Plan-first workflow for Pi using revdiff for interactive markdown plan review.
What it does
This extension adds a lightweight state machine to Pi:
idle→ normal Pi behaviorplanning→ the agent can explore, but may only write/edit markdown plan filesexecuting→ after plan approval, full tools are restored and checklist progress is tracked
The review loop is simple:
- Start plan mode with
/plan - Let the agent explore and write a markdown plan
- The agent calls
plan_submit("PLAN.md") revdiffopens for review- If you quit with no annotations, the plan is approved
- If you annotate lines, the feedback goes back to the agent for revision
- Once approved, execution starts and checklist progress is tracked via
[DONE:n]
Prerequisites
- Node.js 20+ recommended
- Pi coding agent
- revdiff available in
PATH- macOS/Homebrew example:
brew install umputun/apps/revdiff
- macOS/Homebrew example:
- A terminal environment where Pi can launch TUI tools
Install
pi install pi-revdiff-plan
Then verify:
pi list
From source
git clone <this-repo>
cd pi-revdiff-plan
pi install .
Usage
Start in normal mode
pi
Start directly in plan mode
pi --plan
Typical session
/plan
# agent explores codebase and writes PLAN.md
# agent calls plan_submit("PLAN.md")
# revdiff opens for review
# annotate and quit, or quit clean to approve
After approval, the extension restores the previously active tool set and tracks progress using checklist items parsed from the approved markdown file.
Commands
/plan
Toggles plan mode when safe:
idle→planningplanning→idle- during
executing, it does not abort silently; it warns you to use/plan-abort
/plan-abort
Cancels the current execution phase and returns to idle mode.
/plan-status
Shows:
- current phase
- current plan file, if any
- checklist progress
- remaining unchecked steps
Flags
--plan
Starts Pi with plan mode enabled.
Example:
pi --plan
How plan files should look
The agent is prompted to create a markdown plan with sections like:
- Context
- Approach
- Files to modify
- Steps
- Verification
Checklist items should be standard markdown task items, for example:
- [ ] Add parser tests
- [ ] Refactor state restoration
- [ ] Update README
During execution, the extension tracks completion when the agent emits markers like:
[DONE:0]
[DONE:1]
These markers should appear on their own lines.
Validation commands
This project currently uses a minimal validation flow through npm scripts:
npm run typecheck
npm run build
npm run test
npm run lint
npm run validate
Script details
typecheck— run TypeScript with--noEmitbuild— compile project todist/test— build and run Node test suiteslint— currently aliases the type-safe validation baselinevalidate— run typecheck and tests together
Troubleshooting
revdiff binary not found
Make sure revdiff is installed and available in PATH.
You can verify with:
command -v revdiff
You can also point to a custom binary path with REVDIFF_BIN.
Plan submit is rejected
The extension only allows plan files that:
- are inside the current working directory
- end with
.mdor.mdx - exist and are not empty
Examples of rejected paths:
../PLAN.md/absolute/path/outside/repo.mdplan.txt
The agent cannot edit source files in plan mode
That is expected. During planning, write and edit are restricted to markdown files only. Approve the plan first to restore full tool access.
Progress did not update
Checklist progress only updates in executing mode and depends on [DONE:n] markers matching the zero-based checklist index.
Restored session looks wrong
The extension restores plan state from Pi session history. If the approved plan file was deleted or moved, restore falls back to idle.
CI and releases
Recommended repository improvements:
- CI to run type checking and tests on pushes and pull requests
- automated release/versioning flow for publishing
If those files exist in your fork, check .github/workflows/.
Project structure
index.ts # extension entrypoint
src/constants.ts # shared constants
src/parsing.ts # checklist parsing and path validation
src/prompts.ts # agent prompt helpers
src/review.ts # revdiff launch/review flow
src/state.ts # persistence and restore helpers
src/commands.ts # slash commands and flag registration
.pi/extensions/rtk.ts # optional RTK bash rewrite helper
test/*.test.ts # automated tests
License
MIT