@janvitos/pi-plan-build 0.1.49 → 0.1.51

package/README.md

@@ -25,7 +25,7 @@ Optionally keep the approved plan visible in a docked side panel while implement
 ## Features
 
 - New sessions start in **Build** mode.
-- `Ctrl+Tab` cycles **Build → Plan → Build** in every TUI setup. With Pi Plan Build's custom composer active, bare `Tab` also cycles modes while active autocomplete dropdowns retain Pi's normal Tab completion.
+- `Alt+M` cycles **Build → Plan → Build** in every TUI setup. With Pi Plan Build's custom composer active, bare `Tab` also cycles modes while active autocomplete dropdowns retain Pi's normal Tab completion.
 - The custom composer uses OpenCode prompt-inspired blue/orange mode colors on the rounded top-left border and left rail, complemented by Pi's border color on the right rail and rounded bottom-right border; rounded corners inherit their vertical rail colors while horizontal `╌` segments bridge the borders at both junctions, paired with a light vertical `┆` at the top right and a mode-specific bottom-left transition: thin `┆` in Plan and heavy `┇` in Build. The active composer and submitted user messages use a continuous solid thin `│` left rail in both modes. These rails use the active Pi theme's `warning` color in Plan and `thinkingLow` color in Build, and submitted messages retain their original mode after mode changes and session restores. Its metadata row shows mode, model, provider, and thinking level; cycling the thinking level updates that row directly.
 - Pi Plan Build leaves the footer untouched; Pi or another installed extension remains responsible for path, usage, model, provider, thinking, and extension-status information.
 - `/plan`, `/build`, and the `--plan` startup flag.
@@ -41,7 +41,7 @@ Optionally keep the approved plan visible in a docked side panel while implement
 - **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.
 - 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.
 - Staying in Plan mode—or pressing Escape in the approval dialog—produces a durable acknowledgement and stops the run until the user responds.
-- Mode state survives reloads, resumes, and forks.
+- Mode state and mode-specific tool availability survive compactions, reloads, resumes, and forks.
 - 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.
 
 ## Requirements
@@ -80,7 +80,7 @@ Do not install more than one npm, Git, or local copy at the same time; duplicate
 
 | Action | Result |
 | --- | --- |
-| `Ctrl+Tab` | Cycle Build and Plan in any TUI setup |
+| `Alt+M` | Cycle Build and Plan in any TUI setup |
 | `Tab` | With the custom composer active, cycle modes or accept an active autocomplete selection |
 | `/plan` | Select Plan mode |
 | `/build` | Select Build mode |

package/index.ts

@@ -202,7 +202,7 @@ export default function planBuildModes(pi: ExtensionAPI): void {
 		if (!reducedUiNoticeShown) {
 			reducedUiNoticeShown = true;
 			ctx.ui.notify(
-				"Another extension owns Pi's custom editor or fullscreen layout. Pi Plan Build disabled its custom composer and experimental step-by-step panel; Plan and Build workflows remain available through Ctrl+Tab, /plan, and /build.",
+				"Another extension owns Pi's custom editor or fullscreen layout. Pi Plan Build disabled its custom composer and experimental step-by-step panel; Plan and Build workflows remain available through Alt+M, /plan, and /build.",
 				"warning",
 			);
 		}
@@ -343,7 +343,7 @@ export default function planBuildModes(pi: ExtensionAPI): void {
 		description: "Switch to Build mode",
 		handler: async (_args, ctx) => selectMode("build", ctx, "manual"),
 	});
-	pi.registerShortcut("ctrl+tab", {
+	pi.registerShortcut("alt+m", {
 		description: "Cycle Plan and Build modes",
 		handler: async (ctx) => selectMode(nextMode(selectedMode), ctx, "manual"),
 	});
@@ -750,6 +750,10 @@ export default function planBuildModes(pi: ExtensionAPI): void {
 		return { message: { customType: "pi-plan-build-reminder", content, display: false } };
 	});
 
+	pi.on("turn_end", () => {
+		applyTools(runMode ?? selectedMode);
+	});
+
 	pi.on("agent_settled", async (_event, ctx) => {
 		runMode = undefined;
 		applyTools(selectedMode);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@janvitos/pi-plan-build",
-  "version": "0.1.49",
+  "version": "0.1.51",
   "description": "Plan safely, approve explicitly, then implement here or in a clean session.",
   "type": "module",
   "license": "MIT",