@janvitos/pi-plan-build 0.1.0 → 0.1.2

package/README.md

@@ -8,11 +8,12 @@ A global [Pi coding agent](https://github.com/badlogic/pi-mono) extension that a
 
 - New sessions start in **Build** mode.
 - Bare `Tab` cycles **Build → Plan → Build** and replaces normal Tab autocomplete.
-- `[Build]` and `[Plan]` status indicators in Pi's footer.
+- Fixed-width, bold, color-coded **Build** (blue) and **Plan** (yellow) status badges in Pi's footer.
 - `/plan`, `/build`, and the `--plan` startup flag.
 - Per-session plans at `~/.pi/agent/plans/<session-id>.md`.
 - In Plan mode, built-in `edit` and `write` are restricted to the exact plan file.
 - Interactive `question`, `plan_enter`, and `plan_exit` tools.
+- Informational questions are answered directly in Plan mode, with read-only inspection when needed and no plan or approval ceremony.
 - The complete saved plan is rendered in the transcript before approval—without the built-in write preview's truncation.
 - Three approval actions:
   - **Switch to Build and implement here**
@@ -90,6 +91,12 @@ Normal tools remain visible so the model can inspect the project. While a Plan r
 
 This mirrors the intended permission-oriented workflow rather than hiding normal tool schemas.
 
+### Informational questions
+
+Plan mode distinguishes informational Q&A from implementation planning. If a request only asks for an explanation or information, the agent answers directly and ends normally. It may inspect the project with read-only tools when the answer depends on local context, but it does not create or update a plan, ask planning questions unnecessarily, or call `plan_exit`. Plan mode remains selected for the next request.
+
+Requests to change code or produce an implementation plan continue through the normal plan-file and approval workflow.
+
 ## Design and attribution
 
 Pi Plan & Build is an independent extension with its own workflow and UI behavior. Its original mode prompts and transition semantics were informed by OpenCode 1.18.16, while clean-session implementation ideas were informed by the former `pi-plan-mode` extension. Those behaviors have since been adapted and extended for Pi; this project is not affiliated with either project.

package/index.ts

@@ -19,6 +19,7 @@ import {
 	buildPlanReviewMessage,
 	classifyPlanExitChoice,
 	decodeModeState,
+	formatModeStatus,
 	isAllowedPlanMutation,
 	makePlanPath,
 	nextMode,
@@ -94,10 +95,7 @@ export default function planBuildModes(pi: ExtensionAPI): void {
 	}
 
 	function updateStatus(ctx: ExtensionContext): void {
-		const label = selectedMode === "plan"
-			? ctx.ui.theme.fg("warning", "Plan")
-			: ctx.ui.theme.fg("border", "Build");
-		ctx.ui.setStatus(STATUS_KEY, `[${label}]`);
+		ctx.ui.setStatus(STATUS_KEY, formatModeStatus(selectedMode));
 	}
 
 	function discoverUnmanagedTools(): void {
@@ -138,7 +136,6 @@ export default function planBuildModes(pi: ExtensionAPI): void {
 		}
 		updateStatus(ctx);
 		persist();
-		ctx.ui.notify(`${mode === "plan" ? "Plan" : "Build"} mode selected`, "info");
 	}
 
 	pi.registerCommand("plan", {

package/package.json

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

package/prompts.ts

@@ -13,7 +13,17 @@ Plan mode is active. The user indicated that they do not want you to execute yet
 
 ## Plan File Info:
 ${planInfo}
-You should build your plan incrementally by writing to or editing this file. NOTE that this is the only file you are allowed to edit - other than this you are only allowed to take READ-ONLY actions.
+Only when the current request requires an implementation plan should you build the plan incrementally by writing to or editing this file. NOTE that this is the only file you are allowed to edit - other than this you are only allowed to take READ-ONLY actions.
+
+## Informational Questions
+
+If the user asks an informational question and does not ask you to make changes or produce an implementation plan, answer the question directly instead of starting the workflow below.
+
+- You may use read-only tools to inspect the project when the answer depends on it.
+- Do not create or update the plan file.
+- Do not call the question tool merely because the request is phrased as a question; use it only when clarification is actually needed.
+- Do not call plan_exit.
+- End your response normally after answering. Plan mode remains active for future requests.
 
 ## Plan Workflow
 
@@ -66,4 +76,5 @@ Call this tool:
 Do NOT call this tool:
 - Before you have created or finalized the plan
 - If you still have unanswered questions about the implementation
-- If the user has indicated they want to continue planning`;
+- If the user has indicated they want to continue planning
+- After directly answering an informational question that did not require an implementation plan`;

package/utils.ts

@@ -2,6 +2,20 @@ import path from "node:path";
 
 export type Mode = "build" | "plan";
 
+const ANSI_RESET = "\x1b[0m";
+const BOLD_BLACK_FOREGROUND = "1;38;2;0;0;0";
+const MODE_BADGES: Record<Mode, { background: string; text: string; reservedSpace: string }> = {
+	// A trailing reset keeps Pi's status sanitizer from trimming the uncolored reserved cell.
+	plan: { background: "48;2;255;215;0", text: " PLAN ", reservedSpace: "\u00a0" },
+	build: { background: "48;2;59;130;246", text: " BUILD ", reservedSpace: "" },
+};
+
+export function formatModeStatus(mode: Mode): string {
+	const badge = MODE_BADGES[mode];
+	const reservedSuffix = badge.reservedSpace ? `${badge.reservedSpace}${ANSI_RESET}` : "";
+	return `\x1b[${BOLD_BLACK_FOREGROUND};${badge.background}m${badge.text}${ANSI_RESET}${reservedSuffix}`;
+}
+
 export const PLAN_EXIT_APPROVE_CHOICE = "Switch to Build and implement here";
 export const PLAN_EXIT_FRESH_CHOICE = "Start fresh and implement";
 export const PLAN_EXIT_STAY_CHOICE = "Stay in Plan mode";