@janvitos/pi-plan-build 0.1.51 → 0.1.52

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +1 -1
  2. package/index.ts +2 -4
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -41,7 +41,7 @@ Optionally keep the approved plan visible in a docked side panel while implement
41
41
  - **Experimental:** In fullscreen TUI, valid checklist plans also offer **Implement step by step** when Pi Plan Build owns the optional fullscreen layout: a passive, non-overlapping docked right panel keeps the plan visible while natural-language prompts gate steps and report completed work. The panel is visual-only and never captures keyboard input. This feature is still under active development.
42
42
  - Compatible editor decorators can wrap Pi Plan Build's editor without disabling its composer. If another extension replaces rather than invokes that editor, already owns the editor before Plan Build starts, or replaces the fullscreen layout, Plan Build automatically uses reduced UI: it keeps the core Plan/Build workflow and mode status but does not replace that editor or offer a new step-by-step panel.
43
43
  - Staying in Plan mode—or pressing Escape in the approval dialog—produces a durable acknowledgement and stops the run until the user responds.
44
- - Mode state and mode-specific tool availability survive compactions, reloads, resumes, and forks.
44
+ - Plan mode state survives compactions, reloads, resumes, and forks.
45
45
  - When Pi Plan Build's custom editor is active and Pi recreates it, the latest 100 user prompts from the active session branch are restored for Up/Down history navigation.
46
46
 
47
47
  ## Requirements
package/index.ts CHANGED
@@ -606,6 +606,8 @@ export default function planBuildModes(pi: ExtensionAPI): void {
606
606
  name: "plan_exit",
607
607
  label: "Exit Plan Mode",
608
608
  description: PLAN_EXIT_DESCRIPTION,
609
+ promptSnippet: "Display the saved plan and request user approval",
610
+ promptGuidelines: ["Call plan_exit after finalizing the saved plan when the user asks to show, review, or approve it."],
609
611
  parameters: EMPTY_PARAMETERS,
610
612
  executionMode: "sequential",
611
613
  async execute(_toolCallId, _params, _signal, _onUpdate, ctx) {
@@ -750,10 +752,6 @@ export default function planBuildModes(pi: ExtensionAPI): void {
750
752
  return { message: { customType: "pi-plan-build-reminder", content, display: false } };
751
753
  });
752
754
 
753
- pi.on("turn_end", () => {
754
- applyTools(runMode ?? selectedMode);
755
- });
756
-
757
755
  pi.on("agent_settled", async (_event, ctx) => {
758
756
  runMode = undefined;
759
757
  applyTools(selectedMode);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@janvitos/pi-plan-build",
3
- "version": "0.1.51",
3
+ "version": "0.1.52",
4
4
  "description": "Plan safely, approve explicitly, then implement here or in a clean session.",
5
5
  "type": "module",
6
6
  "license": "MIT",