Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,14 @@

All notable changes to `@pi-vault/pi-plan` are documented in this file.

## [Unreleased]

### Changed

- Preserve complete conversation context when switching between Plan mode and normal mode; old display-only proposed-plan messages remain filtered to avoid duplicate context.
- Defer mode changes requested during an active turn until Pi is idle, with the latest queued request taking precedence.
- Submit `Implement the plan.` in the retained conversation instead of copying the full cached plan into a new handoff prompt.

## [0.4.0] - 2026-07-26

Pi 0.82.0 or newer is now required.
Expand Down
8 changes: 5 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,10 +56,10 @@ pi --plan
1. Let the agent inspect the repo and ask clarifying questions.
2. When the plan is ready, you receive exactly one `<proposed_plan>` block.
3. While the agent is idle, choose what to do next:
- **Implement this plan** - turn Plan mode off, restore full tool access, and send the full proposed plan back into the conversation as the implementation instruction.
- **Implement this plan** - turn Plan mode off, restore full tool access, and submit `Implement the plan.` in the same conversation.
- **Save plan** - keep Plan mode active and write the exact current plan to one new lowercase `.md` file in the workspace root. The agent chooses the filename; you do not provide a path.
- **Stay in Plan mode** - keep planning.
- **Exit Plan mode** - leave planning and preserve the latest plan for only the first normal-mode turn.
- **Exit Plan mode** - leave planning without removing prior user or assistant messages. The latest-plan menu cache remains available until the next turn starts.
- **Show latest proposed plan** - review the current plan again.
- **Configure tools** - change which optional tools are available during planning.

Expand All @@ -83,9 +83,11 @@ When you choose it:
| `/plan` | Turn on Plan mode, or open the Plan mode menu if it is already on. |
| `/plan <prompt>` | Turn on Plan mode and send `<prompt>` as the planning request. |
| `/plan:tools` | Open the optional tool selector. If Plan mode is not active yet, Pi enables it first. |
| `/plan:exit` | Turn off Plan mode, restore the previous tool set, and preserve the latest plan for one normal-mode turn. |
| `/plan:exit` | Turn off Plan mode and restore the previous tool set without removing conversation history. |
| `pi --plan` | Start Pi directly in Plan mode. |

If Pi is busy, mode-changing commands and actions from the `/plan` menu wait until the current turn settles. Only the latest queued switch is applied. An automatically opened plan-ready menu cannot queue a mode change until Pi is fully settled; retry with `/plan` if warned. Showing a plan and staying in Plan mode remain immediate; tool configuration requires Pi to be idle.

## Configure Optional Tools

Safe built-in planning tools are available by default. Use `/plan:tools` to enable additional optional extension tools during planning.
Expand Down
Loading