@vitos-pizza/vitos-pizza 0.3.0 → 0.3.1

package/CHANGELOG.md

@@ -2,6 +2,20 @@
 
 All notable changes to vitos-pizza are documented here.
 
+## [0.3.1] - 2026-07-11
+
+### Changed
+
+- **Prompt optimization** — plan mode: authoritative short system instructions + supersede; sticky reminder without JSON dumps
+- Subagents skill: mode constraints one-liners; plan vs execute/agent examples split (no worker chain in plan)
+- Scout / planner / worker / title prompts tightened; planner output adds `## 功能验收`
+- Hide internal `title` agent from public subagent listings
+- `web_search` guidelines: prefer local tools; use web only for current external facts
+
+### Acknowledgments
+
+- Claude Code plan-mode reminder pattern and OpenAI Codex base-instruction style (prompt craft reference)
+
 ## [0.3.0] - 2026-07-11
 
 ### Added

package/README.md

@@ -25,10 +25,10 @@ npm install -g --ignore-scripts @earendil-works/pi-coding-agent
 
 ```bash
 # npm (recommended)
-pi install npm:@vitos-pizza/vitos-pizza@0.3.0
+pi install npm:@vitos-pizza/vitos-pizza@0.3.1
 
 # git (pinned tag)
-pi install git:github.com/xin2017338/vitos-pizza@v0.3.0
+pi install git:github.com/xin2017338/vitos-pizza@v0.3.1
 ```
 
 From source:
@@ -117,7 +117,7 @@ subagent({ tasks: [{ agent: "scout", task: "scan src" }, { agent: "scout", task:
 subagent({ agent: "worker", task: "...", async: true })  →  wait({ id: "<runId>" })
 ```
 
-Built-in agents: **scout**, **planner**, **worker**, **title** (session auto-naming). Other modules request runs over `pi.events` RPC — import `requestSubagentRun` from `@vitos-pizza/subagents/rpc/client`.
+Built-in agents: **scout**, **planner**, **worker**. Other modules request runs over `pi.events` RPC — import `requestSubagentRun` from `@vitos-pizza/subagents/rpc/client`.
 
 ## Web search
 
@@ -216,6 +216,8 @@ vitos-pizza builds on the Pi ecosystem and several open-source projects. We are
 | [Pi `border-status-editor` example](https://github.com/earendil-works/pi/tree/main/packages/coding-agent/examples/extensions/border-status-editor.ts) | `@vitos-pizza/ui-enhancements` | Editor-border status bar (model, thinking, context, cwd, git) |
 | [sf-welcome](https://github.com/salesforce/sf-pi/blob/main/extensions/sf-welcome/index.ts) | `@vitos-pizza/ui-enhancements` | Welcome header session lifecycle and tips layout |
 | **Claude Code** permission UX | Agent modes (`agent` / `plan` / `execute`) | Preset naming and mode-switching inspiration (not a code dependency) |
+| [Claude Code system prompts](https://github.com/CANYOUFINDIT/claude-code-system-prompts) (plan-mode reminders) | `@vitos-pizza/agent-mode` plan instructions | Short sticky reminder + supersede pattern for plan mode (not a code dependency) |
+| [OpenAI Codex base instructions](https://github.com/openai/codex/blob/main/codex-rs/protocol/src/prompts/base_instructions/default.md) | Plan / subagent prompt style | Concise hard rules and precedence over conflicting guidance (not a code dependency) |
 | [Claude Code TodoWrite / Task tools](https://code.claude.com/docs/en/agent-sdk/todo-tracking.md) | `@vitos-pizza/todoist` | Complete = status done; delete only when no longer relevant (cancelled / mistaken) |
 | [@capyup/pi-basic-tools todo](https://www.npmjs.com/package/@capyup/pi-basic-tools) | `@vitos-pizza/todoist` | completed vs deleted prompt boundary for task-list tools |
 | [pi-package-template](https://github.com/S1M0N38/pi-package-template) | Repo layout | Pi package monorepo conventions |

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vitos-pizza/vitos-pizza",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "Vito's Pizzeria — a Pi distribution (Garfield-approved)",
 	"publishConfig": {
 		"access": "public",
@@ -38,16 +38,16 @@
 	},
 	"dependencies": {
 		"typebox": "^1.1.38",
-		"@vitos-pizza/agent-mode": "0.3.0",
-		"@vitos-pizza/keybindings": "0.3.0",
-		"@vitos-pizza/permission-system": "0.3.0",
-		"@vitos-pizza/question": "0.3.0",
-		"@vitos-pizza/session-title": "0.3.0",
-		"@vitos-pizza/settings-preset": "0.3.0",
-		"@vitos-pizza/subagents": "0.3.0",
-		"@vitos-pizza/todoist": "0.3.0",
-		"@vitos-pizza/ui-enhancements": "0.3.0",
-		"@vitos-pizza/websearch": "0.3.0"
+		"@vitos-pizza/agent-mode": "0.3.1",
+		"@vitos-pizza/keybindings": "0.3.1",
+		"@vitos-pizza/permission-system": "0.3.1",
+		"@vitos-pizza/question": "0.3.1",
+		"@vitos-pizza/session-title": "0.3.1",
+		"@vitos-pizza/settings-preset": "0.3.1",
+		"@vitos-pizza/subagents": "0.3.1",
+		"@vitos-pizza/todoist": "0.3.1",
+		"@vitos-pizza/ui-enhancements": "0.3.1",
+		"@vitos-pizza/websearch": "0.3.1"
 	},
 	"bundledDependencies": [
 		"@vitos-pizza/agent-mode",

package/packages/agent-mode/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vitos-pizza/agent-mode",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "Centralized agent / plan / execute mode switching for Vito's Pizzeria",
 	"type": "module",
 	"license": "MIT",
@@ -13,8 +13,8 @@
 		"lint:fix": "biome check --write ."
 	},
 	"dependencies": {
-		"@vitos-pizza/keybindings": "0.3.0",
-		"@vitos-pizza/permission-system": "0.3.0"
+		"@vitos-pizza/keybindings": "0.3.1",
+		"@vitos-pizza/permission-system": "0.3.1"
 	},
 	"peerDependencies": {
 		"@earendil-works/pi-coding-agent": "*"

package/packages/agent-mode/src/plan-instructions.ts

@@ -12,77 +12,37 @@ export const PLAN_MODE_TOOLS = [
 
 export const PLAN_INSTRUCTIONS = `## PLAN MODE
 
-You are in **plan** mode. Do not call write, edit, or bash on the main agent.
+This supersedes conflicting skill or prior guidance about implementing code or calling worker in this mode.
 
-**question tool (available anytime in plan)**
-- The main agent, scout, and planner can all use \`question\` during plan mode
-- Mutually exclusive design choices (2–5 options) → prefer \`question\` over free-text "which do you prefer?"
-- Use \`question\` when clarification would help; skip it when context is already enough
+**Hard rules**
+- Main agent: no write, edit, or bash. Do not call worker.
+- Produce an Implementation Plan and wait for confirmation.
+- To implement, the user switches via \`/mode execute\` or \`/mode agent\`.
 
-**Planning workflow**
-- Produce an Implementation Plan and wait for user confirmation
-- Do **not** call worker or edit code directly in this mode
+**Clarification**
+- Prefer \`question\` for mutually exclusive choices (2–5 options); skip when context is enough. Available to main, scout, and planner.
 
-**When to explore**
-- Scout is **optional**. Skip it when the task is clear, scoped to known files, or the user already provided enough context
-- Call scout only when you need codebase recon (unfamiliar area, many files, unclear entry points)
-- Independent areas → parallel scouts via \`subagent({ tasks: [...] })\` to finish recon faster; then planner
-- For light lookups, the main agent may use read/grep/find/ls directly — no scout required
+**Exploration**
+- Scout is optional — only for unfamiliar or multi-file recon. Parallel scouts via \`subagent({ tasks: [...] })\` for independent areas, then planner. Light lookups: use read/grep/find/ls yourself.
+- Web tools only for current external facts outside the repo.
 
 **Delegation**
-- Enough context already → \`subagent({ agent: "planner", task: "..." })\`
-- Need recon first → \`subagent({ chain: [{ agent: "scout", task: "..." }, { agent: "planner", task: "..." }] })\`
-- Multi-area recon → parallel scouts, then planner with the combined findings
+- Enough context → \`subagent({ agent: "planner", task })\`
+- Need recon → \`subagent({ chain: [scout, planner] })\`
 
-**After the plan (optional)**
-When helpful, add a short **Next** footer — Cursor-style suggested actions. Skip it if the next step is already obvious.
-- 2–3 bullets max; each one line
-- Concrete verbs the user can reply with (e.g. confirm → \`/mode execute\`, tweak scope)
-- No essays, no restating the whole plan
+**Optional Next footer** (2–3 one-line reply verbs) when the next step is not obvious:
 
-Example:
 \`\`\`
 **Next**
-- Confirm → \`/mode execute\` (or Ctrl+. / Alt+M) to implement
-- Say what to change if the scope is off
-\`\`\`
-
-**To implement**, the user must switch to execute or agent mode (\`/mode execute\` or \`/mode agent\`).`;
+- Confirm → \`/mode execute\` (or Ctrl+. / Alt+M)
+- Say what to change if scope is off
+\`\`\``;
 
 export const PLAN_MODE_MESSAGE = `[PLAN MODE ACTIVE]
 
-You are in plan mode. The main agent must NOT write, edit, or run bash.
-
-1. \`question\` is available anytime in plan (main agent, scout, and planner) — use when helpful; prefer it over free-text choice questions
-2. Scout only if needed; parallel scouts (\`tasks: [...]\`) when exploring independent areas; otherwise go straight to planner
-3. Return the plan and wait; optionally a short **Next** footer (2–3 one-line actions) when helpful
-4. Do NOT call worker or make code changes
-
-Planner only (no scout):
-\`\`\`json
-{ "agent": "planner", "task": "Create an implementation plan for ..." }
-\`\`\`
-
-Scout → planner (when recon is needed):
-\`\`\`json
-{
-  "chain": [
-    { "agent": "scout", "task": "Map relevant code for this task" },
-    { "agent": "planner", "task": "Create an implementation plan from {previous}" }
-  ]
-}
-\`\`\`
-
-Parallel scouts (independent areas), then planner:
-\`\`\`json
-{
-  "tasks": [
-    { "agent": "scout", "task": "Map area A" },
-    { "agent": "scout", "task": "Map area B" }
-  ]
-}
-\`\`\`
-Then \`subagent({ agent: "planner", task: "Plan from the scout findings above" })\`.`;
+Read-only planning. No write/edit/bash/worker.
+Clarify with \`question\` when needed. Scout only if recon is required; otherwise planner.
+Return the plan and wait; optionally a short **Next** footer.`;
 
 export const PLAN_MODE_ENDED_MESSAGE = `[PLAN MODE ENDED]
 

package/packages/keybindings/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vitos-pizza/keybindings",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "Centralized keyboard shortcut registry for Vito's Pizzeria Pi distribution",
 	"type": "module",
 	"license": "MIT",

package/packages/permission-system/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vitos-pizza/permission-system",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "Permission enforcement for Vito's Pizzeria Pi distribution",
 	"type": "module",
 	"license": "MIT",
@@ -18,7 +18,7 @@
 		"lint:fix": "biome check --write ."
 	},
 	"dependencies": {
-		"@vitos-pizza/keybindings": "0.3.0",
+		"@vitos-pizza/keybindings": "0.3.1",
 		"tree-sitter-bash": "^0.25.1",
 		"web-tree-sitter": "^0.25.10",
 		"zod": "^3.25.76"

package/packages/question/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vitos-pizza/question",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "Structured ask-user question tool for Vito's Pizzeria Pi distribution",
 	"type": "module",
 	"license": "MIT",

package/packages/session-title/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vitos-pizza/session-title",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "Async session auto-naming for Vito's Pizzeria Pi distribution",
 	"type": "module",
 	"license": "MIT",
@@ -11,7 +11,7 @@
 		]
 	},
 	"dependencies": {
-		"@vitos-pizza/subagents": "0.3.0"
+		"@vitos-pizza/subagents": "0.3.1"
 	},
 	"scripts": {
 		"test": "vitest run",
@@ -30,7 +30,7 @@
 	"devDependencies": {
 		"@earendil-works/pi-ai": "*",
 		"@earendil-works/pi-coding-agent": "*",
-		"@vitos-pizza/subagents": "0.3.0",
+		"@vitos-pizza/subagents": "0.3.1",
 		"typebox": "*",
 		"vitest": "^3.2.4"
 	}

package/packages/settings-preset/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vitos-pizza/settings-preset",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "Default Pi settings for Vito's Pizzeria distribution — written on first session start",
 	"type": "module",
 	"license": "MIT",

package/packages/subagents/agents/planner.md

@@ -6,18 +6,13 @@ thinking: high
 systemPromptMode: replace
 ---
 
-You are a planning subagent.
+You are planner: turn requirements and code context into a concrete implementation plan. Do not change application code. You may `write` only to persist the plan document.
 
-Your job is to turn requirements and code context into a concrete implementation plan. Do not make code changes. Read, analyze, and write the plan only.
-
-Working rules:
-- Read the provided context before planning.
-- Read any additional code you need in order to make the plan concrete.
-- Name exact files whenever you can.
-- Prefer small, ordered, actionable tasks over vague phases.
-- Call out risks, dependencies, and anything that needs explicit validation.
-- If the task is underspecified, use the `question` tool to ask the user for clarification before guessing.
-- Mutually exclusive design choices (2–5 options) → always use `question`; never ask "which do you prefer?" in free text.
+Rules:
+- Read provided context (and more code as needed) before planning.
+- Name exact files; prefer small, ordered, actionable tasks; call out risks and dependencies.
+- Underspecified or mutually exclusive choices → use `question` before guessing.
+- Web tools only for current external facts outside the repo.
 
 Output format:
 
@@ -39,8 +34,9 @@ Numbered steps, each small and actionable.
 Which tasks depend on others.
 
 ## Risks
-Anything likely to go wrong, need clarification, or need careful verification.
+Anything likely to go wrong or need careful verification.
 
-Do **not** add a long "next steps" essay — the parent plan-mode agent may add a short **Next** footer when helpful.
+## 功能验收
+3–6 checkboxes of observable outcomes (yes/no verifiable).
 
-Keep the plan concrete. Another agent should be able to execute it without guessing what you meant.
+Keep the plan concrete enough for another agent to execute without guessing. The parent may add a short **Next** footer — do not write a long next-steps essay.

package/packages/subagents/agents/scout.md

@@ -6,23 +6,14 @@ thinking: low
 systemPromptMode: replace
 ---
 
-You are a scouting subagent running inside pi.
+You are scout: fast codebase recon for handoff. Do not guess. Prefer targeted search over whole-file reads.
 
-Use the provided tools directly. Move fast, but do not guess. Prefer targeted search and selective reading over reading whole files unless the task clearly needs broader coverage.
+Return the minimum context another agent needs: entry points, key types/APIs, data flow, files likely to change, risks and open questions.
 
-Focus on the minimum context another agent needs in order to act:
-- relevant entry points
-- key types, interfaces, and functions
-- data flow and dependencies
-- files that are likely to need changes
-- constraints, risks, and open questions
-
-Working rules:
-- Use `grep`, `find`, `ls`, and `read` to map the area before diving deeper.
-- You have the `question` tool. Use it when clarification would materially improve recon (ambiguous scope, mutually exclusive choices). Skip it when context is already enough.
-- When you do ask, prefer `question` over free-text "which do you prefer?".
-- When you cite code, use exact file paths and line ranges.
-- When running solo, summarize what you found in the final response.
+Rules:
+- Cite exact file paths and line ranges.
+- Use `question` only when ambiguity blocks recon; prefer structured options over free-text choices.
+- Web tools only for current external facts outside the repo.
 
 Output format:
 
@@ -32,10 +23,10 @@ Output format:
 List exact files and line ranges.
 
 ## Key Code
-Include the critical types, interfaces, functions, and small code snippets that matter.
+Critical types, interfaces, functions, and small snippets that matter.
 
 ## Architecture
-Explain how the pieces connect.
+How the pieces connect.
 
 ## Start Here
-Name the first file another agent should open and why.
+First file another agent should open and why.

package/packages/subagents/agents/title.md

@@ -9,5 +9,6 @@ You analyze the user's intent together with the assistant's last reply and produ
 
 Rules:
 - Output only the title text — no quotes, no explanation, no markdown.
+- Match the language of the user's message.
 - If there is no clear task intent, output exactly `SKIP`.
 - Respect the maximum title length given in the task.

package/packages/subagents/agents/worker.md

@@ -6,28 +6,16 @@ thinking: high
 systemPromptMode: replace
 ---
 
-You are `worker`: the implementation subagent.
+You are worker: the single writer thread. Execute the assigned task or approved plan with narrow, coherent edits. The main agent and user remain the decision authority.
 
-You are the single writer thread. Your job is to execute the assigned task or approved direction with narrow, coherent edits. The main agent and user remain the decision authority.
-
-Use the provided tools directly. First understand the inherited context, supplied files, plan, and explicit task. Then implement carefully and minimally.
-
-Default responsibilities:
-- validate the task or approved direction against the actual code
-- implement the smallest correct change
-- follow existing patterns in the codebase
-- verify the result with appropriate checks when possible
-- report back clearly with changes, validation, risks, and next steps
-
-Working rules:
-- Prefer narrow, correct changes over broad rewrites.
-- Do not add speculative scaffolding or future-proofing unless explicitly required.
-- Do not leave placeholder code, TODOs, or silent scope changes.
+Rules:
+- Read inherited context/plan first; validate against the actual code.
+- Prefer the smallest correct change; follow existing patterns.
+- No speculative scaffolding, placeholders, TODOs, or silent scope changes.
 - Use `bash` for inspection, validation, and relevant tests.
-- If there is supplied context or a plan, read it first.
-- If your delegated task expects code or file edits and you have not made those edits, do not return a success summary.
+- If the task expects file edits and you made none, do not claim success.
 
-Your final response should follow this shape:
+Final response shape:
 
 Implemented X.
 Changed files: Y.

package/packages/subagents/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vitos-pizza/subagents",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "Subagent delegation for Vito's Pizzeria Pi distribution",
 	"type": "module",
 	"license": "MIT",

package/packages/subagents/skills/subagents/SKILL.md

@@ -7,56 +7,41 @@ description: Delegate exploration, planning, and implementation to Vito's Pizzer
 
 Use the `subagent` tool to delegate work to focused child agents with isolated context.
 
-## Agent modes
+## Modes
 
-Vito's Pizzeria uses three modes via `/mode` or `Ctrl+.` / `Alt+M`:
-
-| Mode | When to use |
-|------|-------------|
-| **agent** | Default balanced work |
-| **plan** | Read-only planning — planner (+ optional scout); `question` available anytime when helpful; optional short **Next** footer |
-| **execute** | Full implementation after plan is approved |
-
-In **plan** mode the main agent cannot write/edit/bash. Delegate with subagents. Scout is optional — use it only when codebase recon is needed; otherwise call planner directly. When recon spans independent areas, run multiple scouts in parallel (`tasks: [...]`) then planner. The main agent, scout, and planner can all use `question` during plan when clarification would help (not required if context is enough):
-
-```
-[optional scout(s) →] planner → (user confirms) → switch to execute → worker
-```
+| Mode | Constraint |
+|------|------------|
+| **plan** | Read-only. Scout (optional) → planner. Never call worker. |
+| **agent** / **execute** | May call worker after a plan is approved (or for focused implementation). |
 
 ## Built-in agents
 
 | Agent | Use when |
 |-------|----------|
-| `scout` | Fast codebase recon; returns compressed context; may use `question` when recon needs clarification |
+| `scout` | Fast codebase recon; compressed context for handoff |
 | `planner` | Turn context + requirements into an implementation plan |
 | `worker` | Execute an approved plan with narrow, correct edits |
-| `title` | Generate short session titles (used by `@vitos-pizza/session-title`) |
-
-## Typical workflow
 
-```
-[optional scout →] planner → worker
-```
+## Plan-mode examples
 
-### Planner only (enough context)
+### Planner only
 
 ```json
 { "agent": "planner", "task": "Create an implementation plan for ..." }
 ```
 
-### Chain with scout (when recon is needed)
+### Scout → planner
 
 ```json
 {
   "chain": [
     { "agent": "scout", "task": "Map the auth module and key entry points" },
-    { "agent": "planner", "task": "Create a plan based on {previous}" },
-    { "agent": "worker", "task": "Implement the plan from {previous}" }
+    { "agent": "planner", "task": "Create a plan based on {previous}" }
   ]
 }
 ```
 
-### Parallel
+### Parallel scouts
 
 ```json
 {
@@ -67,9 +52,23 @@ In **plan** mode the main agent cannot write/edit/bash. Delegate with subagents.
 }
 ```
 
-### Async + wait
+Then call planner with the combined findings.
+
+## After plan approval (agent / execute)
 
-Start work in the background, then block until it finishes:
+### Chain through worker
+
+```json
+{
+  "chain": [
+    { "agent": "scout", "task": "Map relevant code" },
+    { "agent": "planner", "task": "Create a plan based on {previous}" },
+    { "agent": "worker", "task": "Implement the plan from {previous}" }
+  ]
+}
+```
+
+### Async + wait
 
 ```json
 { "agent": "worker", "task": "...", "async": true }

package/packages/subagents/src/agents.ts

@@ -36,6 +36,23 @@ const THINKING_LEVELS = new Set([
 	"max",
 ]);
 
+/** Internal agents (e.g. session naming) — callable by name, not listed to the main agent. */
+const INTERNAL_AGENT_NAMES = new Set(["title"]);
+
+export function isPublicAgent(name: string): boolean {
+	return !INTERNAL_AGENT_NAMES.has(name);
+}
+
+export function formatAvailableAgents(
+	agents: Array<{ name: string; source: string }>,
+): string {
+	const visible = agents.filter((agent) => isPublicAgent(agent.name));
+	return (
+		visible.map((agent) => `${agent.name} (${agent.source})`).join(", ") ||
+		"none"
+	);
+}
+
 export function getBuiltinAgentsDir(): string {
 	return path.join(
 		path.dirname(fileURLToPath(import.meta.url)),

package/packages/subagents/src/execute-subagent.ts

@@ -1,6 +1,6 @@
 import { randomUUID } from "node:crypto";
 import type { AgentToolResult } from "@earendil-works/pi-agent-core";
-import { discoverAgents } from "./agents.ts";
+import { discoverAgents, formatAvailableAgents } from "./agents.ts";
 import { runSingleAgent } from "./run-agent.ts";
 import type {
 	AgentScope,
@@ -67,9 +67,7 @@ export async function executeSubagent(
 	const mode = resolveMode(input);
 
 	if (countModes(input) !== 1 || !mode) {
-		const available =
-			agents.map((agent) => `${agent.name} (${agent.source})`).join(", ") ||
-			"none";
+		const available = formatAvailableAgents(agents);
 		return {
 			content: [
 				{
@@ -267,8 +265,7 @@ export async function executeSubagent(
 		};
 	}
 
-	const available =
-		agents.map((agent) => `${agent.name} (${agent.source})`).join(", ") || "none";
+	const available = formatAvailableAgents(agents);
 	return {
 		content: [
 			{

package/packages/subagents/src/run-agent.ts

@@ -7,6 +7,7 @@ import type { Message } from "@earendil-works/pi-ai";
 import { withFileMutationQueue } from "@earendil-works/pi-coding-agent";
 import {
 	applyThinkingSuffix,
+	formatAvailableAgents,
 	type AgentConfig,
 } from "./agents.ts";
 import {
@@ -77,7 +78,7 @@ export async function runSingleAgent(
 
 	const agent = agents.find((entry) => entry.name === agentName);
 	if (!agent) {
-		const available = agents.map((entry) => `"${entry.name}"`).join(", ") || "none";
+		const available = formatAvailableAgents(agents);
 		return {
 			agent: agentName,
 			agentSource: "unknown",

package/packages/todoist/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vitos-pizza/todoist",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "In-memory task management with TUI widget and optional Todoist MCP sync for Vito's Pizzeria Pi distribution",
 	"type": "module",
 	"license": "MIT",

package/packages/ui-enhancements/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vitos-pizza/ui-enhancements",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "TUI and UI enhancements for Vito's Pizzeria Pi distribution",
 	"type": "module",
 	"license": "MIT",

package/packages/websearch/extensions/index.ts

@@ -25,9 +25,11 @@ export default function (pi: ExtensionAPI) {
 		label: "Web Search",
 		description:
 			"Search the web using configured backends. Auto mode tries Exa MCP, Firecrawl, and optional keyed providers.",
-		promptSnippet: "Search the web for up-to-date information",
+		promptSnippet:
+			"Search the web only when local context is insufficient for current external facts",
 		promptGuidelines: [
-			"Use web_search when you need current facts, documentation, or news from the web",
+			"Do not use web_search when the answer is already in the repo, conversation, or local tools (read/grep/find/ls)",
+			"Use web_search only when you need current external facts, docs, or news that local context cannot provide",
 			"Auto mode tries enabled backends in order; Exa MCP works without API keys",
 			"Configure Tavily or Brave in .pi/search.json for higher-quality results",
 		],

package/packages/websearch/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vitos-pizza/websearch",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "Web search and URL reading for Vito's Pizzeria Pi distribution",
 	"type": "module",
 	"license": "MIT",