@narumitw/pi-plan-mode 0.1.17 → 0.1.19

package/README.md

@@ -14,6 +14,7 @@ Pi core intentionally does not ship a built-in plan mode; this package provides
 - Blocks mutating bash commands such as `rm`, `git commit`, dependency installs, redirects, and editor launches.
 - Injects Codex-like Plan mode instructions: explore first, ask only non-discoverable questions, do not mutate files, and finish with `<proposed_plan>`.
 - Detects proposed plan blocks and prompts you to implement, revise, or stay in Plan mode.
+- Shows Plan mode state in Pi's statusline as `📝 plan active` or `📝 plan ready`.
 - Persists Plan mode state in the Pi session so resume restores the mode.
 
 ## 📦 Install
@@ -38,8 +39,11 @@ pi -e ./extensions/pi-plan-mode
 
 ```text
 /plan
+/plan <prompt>
 ```
 
+Use `/plan` to enter Plan mode before writing your planning prompt. Use `/plan <prompt>` to enter Plan mode and immediately submit `<prompt>` as the first Plan-mode user message.
+
 When Plan mode is active, ask the agent to design the change. The agent may inspect files and run read-only commands, but it should not edit files or execute the implementation.
 
 A complete Plan mode answer should include exactly one block like this:
@@ -62,7 +66,12 @@ A complete Plan mode answer should include exactly one block like this:
 </proposed_plan>
 ```
 
-After a proposed plan is detected, `/plan` lets you choose whether to implement the plan, revise it, stay in Plan mode, or exit Plan mode.
+After a proposed plan is detected, `/plan` lets you choose whether to implement the plan, revise it, stay in Plan mode, or exit Plan mode. Choosing implementation disables Plan mode, restores full tool access, and immediately starts an implementation turn with the proposed plan.
+
+While Plan mode is enabled, the extension also publishes a compact status for Pi statuslines. With `@narumitw/pi-statusline`, this appears in the extension status area:
+
+- `📝 plan active`: Plan mode is enabled and still gathering context or drafting a plan.
+- `📝 plan ready`: A `<proposed_plan>` was detected and is waiting for your next `/plan` action.
 
 You can also exit directly:
 
@@ -75,8 +84,9 @@ You can also exit directly:
 This extension maps Codex's `ModeKind::Plan` behavior onto Pi's extension API:
 
 - Plan mode is a conversational collaboration mode, not TODO/progress tracking.
+- `/plan <prompt>` follows Codex behavior by switching to Plan mode before submitting the inline prompt.
 - `update_plan`-style checklist use is discouraged while Plan mode is active.
-- The implementation boundary is explicit: Plan mode restores tools only after you choose to leave it.
+- The implementation boundary is explicit: Plan mode restores tools before starting implementation, and choosing implementation immediately triggers a normal agent turn with full tool access.
 - Pi extension safety is approximated with active-tool restriction plus bash filtering, so it may be stricter or looser than Codex core in edge cases.
 
 ## 🗂️ Package layout

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@narumitw/pi-plan-mode",
-	"version": "0.1.17",
+	"version": "0.1.19",
 	"description": "Pi extension that adds a Codex-like read-only /plan collaboration mode.",
 	"type": "module",
 	"license": "MIT",

package/src/plan-mode.ts

@@ -88,12 +88,17 @@ export default function planMode(pi: ExtensionAPI) {
 	pi.registerCommand("plan", {
 		description: "Enter or manage Codex-like Plan mode",
 		handler: async (args, ctx) => {
-			const command = args.trim().toLowerCase();
+			const prompt = args.trim();
+			const command = prompt.toLowerCase();
 			if (command === "exit" || command === "off") {
 				exitPlanMode(ctx);
 				ctx.ui.notify("Plan mode disabled. Full tool access restored.", "info");
 				return;
 			}
+			if (prompt) {
+				enterPlanModeWithPrompt(prompt, ctx);
+				return;
+			}
 			if (!state.enabled) {
 				enterPlanMode(ctx);
 				ctx.ui.notify("Plan mode enabled. I will explore and plan, but not modify files.", "info");
@@ -186,6 +191,16 @@ export default function planMode(pi: ExtensionAPI) {
 		updateUi(ctx);
 	}
 
+	function enterPlanModeWithPrompt(prompt: string, ctx: ExtensionContext) {
+		const wasEnabled = state.enabled;
+		enterPlanMode(ctx);
+		if (!wasEnabled) {
+			ctx.ui.notify("Plan mode enabled. I will explore and plan, but not modify files.", "info");
+		}
+		if (ctx.isIdle()) pi.sendUserMessage(prompt);
+		else pi.sendUserMessage(prompt, { deliverAs: "followUp" });
+	}
+
 	function exitPlanMode(ctx: ExtensionContext) {
 		state = { ...state, enabled: false, awaitingAction: false };
 		restoreTools();
@@ -193,6 +208,25 @@ export default function planMode(pi: ExtensionAPI) {
 		updateUi(ctx);
 	}
 
+	function startImplementation(ctx: ExtensionContext) {
+		const plan = state.latestPlan?.trim();
+		exitPlanMode(ctx);
+
+		if (!plan) {
+			ctx.ui.notify("Plan mode disabled. No proposed plan is available to implement.", "warning");
+			return;
+		}
+
+		pi.sendMessage(
+			{
+				customType: "plan-mode-implementation",
+				content: `Plan mode is now disabled. Full tool access is restored. Implement this proposed plan now:\n\n${plan}`,
+				display: true,
+			},
+			{ triggerTurn: true },
+		);
+	}
+
 	async function showPlanMenu(ctx: ExtensionContext) {
 		if (!ctx.hasUI) {
 			ctx.ui.notify(planStatusText(), "info");
@@ -207,7 +241,11 @@ export default function planMode(pi: ExtensionAPI) {
 			ctx.ui.notify(state.latestPlan ?? "No proposed plan yet.", "info");
 			return;
 		}
-		if (choice === "Implement this plan" || choice === "Exit Plan mode") {
+		if (choice === "Implement this plan") {
+			startImplementation(ctx);
+			return;
+		}
+		if (choice === "Exit Plan mode") {
 			exitPlanMode(ctx);
 			ctx.ui.notify("Plan mode disabled. Full tool access restored.", "info");
 			return;
@@ -222,8 +260,7 @@ export default function planMode(pi: ExtensionAPI) {
 			"Stay in Plan mode",
 		]);
 		if (choice === "Implement this plan") {
-			exitPlanMode(ctx);
-			ctx.ui.notify("Plan mode disabled. Ask me to implement the proposed plan when ready.", "info");
+			startImplementation(ctx);
 			return;
 		}
 		if (choice === "Revise plan") {
@@ -268,7 +305,7 @@ export default function planMode(pi: ExtensionAPI) {
 	}
 
 	function updateUi(ctx: ExtensionContext) {
-		ctx.ui.setStatus(STATUS_KEY, state.enabled ? "plan: active" : undefined);
+		ctx.ui.setStatus(STATUS_KEY, formatStatus());
 		if (state.enabled && state.latestPlan) {
 			ctx.ui.setWidget(PLAN_WIDGET_KEY, [
 				"Proposed plan ready",
@@ -281,6 +318,12 @@ export default function planMode(pi: ExtensionAPI) {
 		}
 	}
 
+	function formatStatus() {
+		if (!state.enabled) return undefined;
+		if (state.awaitingAction || state.latestPlan) return "📝 plan ready";
+		return "📝 plan active";
+	}
+
 	function clearUi(ctx: ExtensionContext) {
 		ctx.ui.setStatus(STATUS_KEY, undefined);
 		ctx.ui.setWidget(PLAN_WIDGET_KEY, undefined);