@oh-my-pi/pi-coding-agent 10.2.1 → 10.2.3

package/src/prompts/tools/ask.md

@@ -1,38 +1,35 @@
 # Ask
 
-Ask the user a question when you need clarification or input during task execution.
+Ask user when you need clarification or input during task execution.
 
 <conditions>
 - Clarify ambiguous requirements before implementing
 - Get decisions on implementation approach when multiple valid options exist
-- Request user preferences (styling, naming conventions, architecture patterns)
+- Request preferences (styling, naming conventions, architecture patterns)
 - Offer meaningful choices about task direction
 </conditions>
 
 <instruction>
-- Use `recommended: <index>` to mark the default option (0-indexed); " (Recommended)" suffix is added automatically
-- Use `questions` array for multiple related questions instead of asking one at a time
-- Set `multi: true` on a question to allow multiple selections
+- Use `recommended: <index>` to mark default (0-indexed); " (Recommended)" added automatically
+- Use `questions` for multiple related questions instead of asking one at a time
+- Set `multi: true` on question to allow multiple selections
 </instruction>
 
 <output>
-Returns user's selected option(s) as text. For multi-part questions, returns a map of question IDs to selected values.
+Returns selected option(s) as text. For multi-part questions, returns map of question IDs to selected values.
 </output>
 
 <important>
 - Provide 2-5 concise, distinct options
-- Users can always select "Other" for custom input (UI adds this automatically)
 </important>
 
 <critical>
-**Exhaust all other options before asking.** Questions interrupt user flow.
-1. **Unknown file location?** → Search with grep/find first. Only ask if search fails.
-2. **Ambiguous syntax/format?** → Infer from context and codebase conventions. Make a reasonable choice.
-3. **Missing details?** → Check docs, related files, commit history. Fill gaps yourself.
-4. **Implementation approach?** → Choose based on codebase patterns. Ask only for genuinely novel architectural decisions.
-
-If you can make a reasonable inference from the user's request, **do it**. Users communicate intent, not specifications—your job is to translate intent into correct implementation.
-**Do NOT include an "Other" option in your options array.** The UI automatically adds "Other (type your own)" to every question. Adding your own creates duplicates.
+**Exhaust all other options before asking.**
+1. **Unknown file location?** → Search with grep/find first; ask only if search fails.
+2. **Ambiguous syntax/format?** → Infer from context and codebase conventions; make reasonable choice.
+3. **Missing details?** → Check docs, related files, commit history; fill gaps yourself.
+4. **Implementation approach?** → Choose based on codebase patterns; ask only for genuinely novel architectural decisions.
+**Do NOT include "Other" option in your options array.** UI automatically adds "Other (type your own)" to every question; adding your own creates duplicates.
 </critical>
 
 <example name="single">

package/src/prompts/tools/bash.md

@@ -1,6 +1,6 @@
 # Bash
 
-Executes a bash command in a shell session for terminal operations like git, bun, cargo, python.
+Executes bash command in shell session for terminal operations like git, bun, cargo, python.
 
 <instruction>
 - Use `cwd` parameter to set working directory instead of `cd dir && ...`
@@ -11,9 +11,9 @@ Executes a bash command in a shell session for terminal operations like git, bun
 </instruction>
 
 <output>
-Returns stdout, stderr, and exit code from command execution.
-- Output truncated after 50KB or 2000 lines (whichever comes first); use `head` parameter to limit output
-- If output is truncated, full output is stored under $ARTIFACTS and referenced as `artifact://<id>` in metadata
+Returns stdout, stderr, exit code from command execution.
+- Output truncated after 50KB or 2000 lines (whichever first); use `head` parameter to limit output
+- If output truncated, full output stored under $ARTIFACTS and referenced as `artifact://<id>` in metadata
 - Exit codes shown on non-zero exit; stderr captured
 </output>
 
@@ -27,11 +27,11 @@ Do NOT use Bash for these operations—specialized tools exist:
 </critical>
 
 <avoid>
-Do NOT pipe through `head` or `tail`—use the `head` and `tail` parameters instead:
+Do NOT pipe through `head` or `tail`—use `head` and `tail` parameters instead:
 - `command | head -n 50` → use `head: 50` parameter
 - `command | tail -n 100` → use `tail: 100` parameter
 
-The pipe pattern breaks streaming output and prevents artifact storage.
+Pipe pattern breaks streaming output and prevents artifact storage.
 
-Do NOT use `2>&1`—stdout and stderr are already merged.
+Do NOT use `2>&1`—stdout and stderr already merged.
 </avoid>

package/src/prompts/tools/exit-plan-mode.md

@@ -1,15 +1,15 @@
-Signals plan completion and requests user approval to begin implementation.
+Signals plan completion, requests user approval to begin implementation.
 
 <conditions>
 Use when:
-- Plan is written to the plan file
+- Plan written to plan file
 - No unresolved questions about requirements or approach
-- Ready for user to review and approve
+- Ready for user review and approval
 </conditions>
 
 <instruction>
-- Write your plan to the plan file BEFORE calling this tool
-- This tool reads the plan from that file—does not take plan content as parameter
+- Write plan to plan file BEFORE calling this tool
+- Tool reads plan from file—does not take plan content as parameter
 - User sees plan contents when reviewing
 </instruction>
 
@@ -28,7 +28,7 @@ Unsure about auth method (OAuth vs JWT).
 </example>
 
 <avoid>
-- Calling before plan is written to file
+- Calling before plan written to file
 - Using `ask` to request plan approval (this tool does that)
 - Calling after pure research tasks (no implementation planned)
 </avoid>

package/src/prompts/tools/gemini-image.md

@@ -3,21 +3,21 @@
 Generate or edit images using Gemini image models.
 
 <instruction>
-Provide structured parameters for best results. The tool assembles them into an optimized prompt.
+Provide structured parameters for best results. Tool assembles into optimized prompt.
 
-When using multiple `input_images`, describe each image's role in the `subject` or `scene` field:
+When using multiple `input_images`, describe each image's role in `subject` or `scene` field:
 - "Use Image 1 for the character's face and outfit, Image 2 for the pose, Image 3 for the background environment"
 - "Match the color palette from Image 1, apply the lighting style from Image 2"
 </instruction>
 
 <output>
-Returns the generated image saved to disk. The response includes the file path where the image was written.
+Returns generated image saved to disk. Response includes file path where image was written.
 </output>
 
 <important>
 - For photoreal: add "ultra-detailed, realistic, natural skin texture" to style
 - For posters/cards: use 9:16 aspect ratio with negative space for text placement
-- For iteration: use `changes` to make targeted adjustments rather than regenerating from scratch
+- For iteration: use `changes` for targeted adjustments rather than regenerating from scratch
 - For text: add "sharp, legible, correctly spelled" for important text; keep text short
 - For diagrams: include "scientifically accurate" in style and provide facts explicitly
 </important>

package/src/prompts/tools/grep.md

@@ -1,6 +1,6 @@
 # Grep
 
-A powerful search tool built on ripgrep.
+Powerful search tool built on ripgrep.
 
 <instruction>
 - Supports full regex syntax (e.g., `log.*Error`, `function\\s+\\w+`)
@@ -15,12 +15,12 @@ Results depend on `output_mode`:
 - `files_with_matches`: File paths only (one per line)
 - `count`: Match counts per file
 
-In `content` mode, truncated at 100 matches by default (configurable via `limit`).
-For `files_with_matches` and `count` modes, use `limit` to truncate results.
+In `content` mode, truncated at 100 matches default (configurable via `limit`).
+For `files_with_matches` and `count` modes, use `limit` truncate results.
 </output>
 
 <critical>
-- ALWAYS use Grep for search tasks—NEVER invoke `grep` or `rg` via Bash. This tool has correct permissions and access.
+- ALWAYS use Grep for search tasks—NEVER invoke `grep` or `rg` via Bash. Has correct permissions and access.
 </critical>
 
 <avoid>

package/src/prompts/tools/lsp.md

@@ -3,33 +3,26 @@
 Interact with Language Server Protocol servers for code intelligence.
 
 <operations>
-- `diagnostics`: Get errors/warnings for a file
-- `workspace_diagnostics`: Check entire project (uses tsc, cargo check, go build, etc.)
 - `definition`: Go to symbol definition
-- `references`: Find all references to a symbol
+- `references`: Find all references to symbol
 - `hover`: Get type info and documentation
-- `symbols`: List symbols in a file (functions, classes, etc.)
-- `workspace_symbols`: Search for symbols across the project
-- `rename`: Rename a symbol across the codebase
-- `actions`: List and apply code actions (quick fixes, refactors)
-- `incoming_calls`: Find all callers of a function
-- `outgoing_calls`: Find all functions called by a function
+- `symbols`: List symbols in file, or search workspace (with query, no file)
+- `rename`: Rename symbol across codebase
+- `diagnostics`: Get errors/warnings for file, or check entire project (no file)
+- `reload`: Restart the language server
 </operations>
 
 <output>
-Returns vary by operation:
-- `diagnostics`/`workspace_diagnostics`: List of errors/warnings with file, line, severity, message
-- `definition`: File path and position of the definition
-- `references`: List of locations (file + position) where symbol is used
+- `definition`: File path and position of definition
+- `references`: List of locations (file + position) where symbol used
 - `hover`: Type signature and documentation text
-- `symbols`/`workspace_symbols`: List of symbol names, kinds, and locations
+- `symbols`: List of symbol names, kinds, locations
 - `rename`: Confirmation of changes made across files
-- `actions`: List of available code actions; when applied, returns the result
-- `incoming_calls`/`outgoing_calls`: Call hierarchy with caller/callee locations
+- `diagnostics`: List of errors/warnings with file, line, severity, message
+- `reload`: Confirmation of server restart
 </output>
 
 <important>
-- Requires a running LSP server for the target language
-- Some operations require the file to be saved to disk
-- `workspace_diagnostics` may be slow on large projects
+- Requires running LSP server for target language
+- Some operations require file to be saved to disk
 </important>

package/src/prompts/tools/patch.md

@@ -1,56 +1,54 @@
 # Edit
 
-Performs patch operations on a file given a diff. Primary tool for modifying existing files.
+Patch operations on file given diff. Primary tool for existing-file edits.
 
 <instruction>
 **Hunk Headers:**
-- `@@` — bare header when context lines are already unique
-- `@@ $ANCHOR` — anchor must be copied verbatim from the file (full line or unique substring)
-**Anchor Selection Algorithm:**
-1. If surrounding context lines are already unique, use bare `@@`
-2. Otherwise choose a highly specific anchor copied from the file:
-   - full function signature line
-   - class declaration line
-   - unique string literal / error message
+- `@@` — bare header when context lines unique
+- `@@ $ANCHOR` — anchor copied verbatim from file (full line or unique substring)
+**Anchor Selection:**
+1. Otherwise choose highly specific anchor copied from file:
+   - full function signature
+   - class declaration
+   - unique string literal/error message
    - config key with uncommon name
-3. If "Found multiple matches" error: add more context lines, use multiple hunks with separate anchors, or use a longer anchor substring
+2. On "Found multiple matches": add context lines, use multiple hunks with separate anchors, or use longer anchor substring
 **Context Lines:**
-- Include enough ` `-prefixed lines to make match unique (usually 2–8 total)
-- Must exist in the file exactly as written (preserve indentation/trailing spaces)
-- When editing structured blocks (nested braces, tags, indented regions), include opening and closing lines in context so the edit stays inside the block
+Use enough ` `-prefixed lines to make match unique (usually 2–8)
+When editing structured blocks (nested braces, tags, indented regions), include opening and closing lines so edit stays inside block
 </instruction>
 
 <parameters>
 ```ts
 type T =
-   // Diff is one or more hunks, within the same file.
-   // - Each hunk begins with "@@" (optionally with an anchor).
-   // - Each hunk body contains only lines starting with: ' ' | '+' | '-'.
-   // - Each hunk must include at least one real change (+ or -). No no-op hunks.
+   // Diff is one or more hunks in the same file.
+   // - Each hunk begins with "@@" (anchor optional).
+   // - Each hunk body only has lines starting with ' ' | '+' | '-'.
+   // - Each hunk includes at least one change (+ or -).
    | { path: string, op: "update", diff: string }
-   // Diff is the full file content, no prefixes.
+   // Diff is full file content, no prefixes.
    | { path: string, op: "create", diff: string }
-   // Omit diff for delete operation.
+   // No diff for delete.
    | { path: string, op: "delete" }
-   // New path for update-and-move operation.
+   // New path for update+move.
    | { path: string, op: "update", rename: string, diff: string }
 ```
 </parameters>
 
 <output>
-Returns success/failure status. On failure, returns error message indicating:
+Returns success/failure; on failure, error message indicates:
 - "Found multiple matches" — anchor/context not unique enough
 - "No match found" — context lines don't exist in file (wrong content or stale read)
 - Syntax errors in diff format
 </output>
 
 <critical>
-- Always read the target file before editing
+- Always read target file before editing
 - Copy anchors and context lines verbatim (including whitespace)
-- Never use anchors as comments (no line numbers, location labels, or placeholders like `@@ @@`)
-- Do not place new lines outside the intended block unless that is the explicit goal
-- If an edit fails or produces broken structure, re-read the file and produce a new patch from current content—do not retry the same diff
-- If indentation is wrong after editing, run the project's formatter (if available) rather than making repeated edit attempts
+- Never use anchors as comments (no line numbers, location labels, placeholders like `@@ @@`)
+- Do not place new lines outside intended block
+- If edit fails or breaks structure, re-read file and produce new patch from current content—do not retry same diff
+- If indentation/alignment wrong after editing, run formatter (`go fmt`, `cargo fmt`, `ruff format`, `biome`, etc.)—never make repeated edit attempts to fix whitespace
 </critical>
 
 <example name="create">
@@ -71,8 +69,6 @@ edit {"path":"obsolete.txt","op":"delete"}
 
 <avoid>
 - Generic anchors: `import`, `export`, `describe`, `function`, `const`
-- Anchor comments: `line 207`, `top of file`, `near imports`, `...`
-- Editing without reading the file first (causes stale context errors)
-- Repeating the same addition in multiple hunks (creates duplicate blocks)
-- Falling back to full-file overwrites for minor changes (acceptable for major restructures or short files)
+- Repeating same addition in multiple hunks (duplicate blocks)
+- Full-file overwrites for minor changes (acceptable for major restructures or short files)
 </avoid>

package/src/prompts/tools/python.md

@@ -1,19 +1,17 @@
 # Python
 
-Executes Python cells sequentially in a persistent IPython kernel.
+Runs Python cells sequentially in persistent IPython kernel.
 
 <instruction>
-The kernel persists between calls and between cells. **Imports, variables, and functions survive.** Use this.
+Kernel persists across calls and cells; **imports, variables, and functions survive—use this.**
 **Work incrementally:**
-- One logical step per cell (imports, define a function, test it, use it)
-- Pass multiple small cells in one call—they execute sequentially
+- One logical step per cell (imports, define function, test it, use it)
+- Pass multiple small cells in one call
 - Define small functions you can reuse and debug individually
-- Put explanations in the assistant message or cell title, **not** inside code
+- Put explanations in assistant message or cell title, **not** in code
 **When something fails:**
-- The error tells you which cell failed (e.g., "Cell 3 failed")
-- Earlier cells already ran—their state persists in the kernel
-- Resubmit with only the fixed cell (or the fixed cell + remaining cells)
-- Do NOT rewrite working cells or re-import modules
+- Errors tell you which cell failed (e.g., "Cell 3 failed")
+- Resubmit only fixed cell (or fixed cell + remaining cells)
 </instruction>
 
 <prelude>
@@ -36,26 +34,23 @@ All helpers auto-print results and return values for chaining.
 </prelude>
 
 <output>
-Output streams in real time, truncated after 100KB.
-If output is truncated, full output is stored under $ARTIFACTS and referenced as `artifact://<id>` in metadata.
+Streams in real time, truncated after 100KB; if truncated, full output stored under $ARTIFACTS and referenced as `artifact://<id>` in metadata.
 
-The user sees output like a Jupyter notebook—rich displays are fully rendered:
+User sees output like Jupyter notebook; rich displays render fully:
 - `display(JSON(data))` → interactive JSON tree
 - `display(HTML(...))` → rendered HTML
 - `display(Markdown(...))` → formatted markdown
 - `plt.show()` → inline figures
-**You will see object repr** (e.g., `<IPython.core.display.JSON object>`) **but the user sees the rendered output.** Trust that `display()` calls work correctly—do not assume the user sees only the repr.
+**You will see object repr** (e.g., `<IPython.core.display.JSON object>`). Trust `display()`; do not assume user sees only repr.
 </output>
 
 <important>
-- Kernel persists for the session by default; per-call mode uses a fresh kernel each call
-- Use `reset: true` to clear state when session mode is active
+- Per-call mode uses fresh kernel each call
+- Use `reset: true` to clear state when session mode active
 </important>
 
 <critical>
-- Use `plt.show()` to display figures
-- Use `display()` from IPython.display for rich output (HTML, Markdown, images, etc.)
-- Use `sh()` or `run()` for shell commands, never raw `subprocess`
+- Use `run()` for shell commands; never raw `subprocess`
 </critical>
 
 <example name="good">
@@ -68,42 +63,4 @@ cells: [
     {"title": "use helper", "code": "configs = [parse_config(p) for p in Path('.').glob('*.json')]"}
 ]
 ```
-</example>
-
-<example name="prelude-helpers">
-```python
-# Concatenate all markdown files in docs/
-cat(*find("*.md", "docs"))
-
-# Mass rename: foo -> bar across all .py files
-rsed(r'\bfoo\b', 'bar', glob_pattern="*.py")
-
-# Process files in batch
-batch(find("*.json"), lambda p: json.loads(p.read_text()))
-
-# Sort and deduplicate lines
-sort_lines(read("data.txt"), unique=True)
-
-# Extract columns 0 and 2 from TSV
-cols(read("data.tsv"), 0, 2, sep="\t")
-```
-</example>
-
-<example name="shell-commands">
-```python
-# Good
-sh("bun run check")
-run("cargo build --release")
-
-# Bad - never use subprocess directly
-import subprocess
-subprocess.run(["bun", "run", "check"], ...)
-```
-</example>
-
-<avoid>
-- Putting everything in one giant cell
-- Re-importing modules you already imported
-- Rewriting working cells when only one part failed
-- Large functions that are hard to debug piece by piece
-</avoid>
+</example>

package/src/prompts/tools/read.md

@@ -1,13 +1,13 @@
 # Read
 
-Reads files from the local filesystem or internal URLs.
+Reads files from local filesystem or internal URLs.
 
 <instruction>
-- Reads up to {{DEFAULT_MAX_LINES}} lines by default
+- Reads up to {{DEFAULT_MAX_LINES}} lines default
 - Use `offset` and `limit` for large files
-- Use `lines: true` to include line numbers
+- Use `lines: true` include line numbers
 - Supports images (PNG, JPG) and PDFs
-- For directories, use the ls tool instead
+- For directories, returns formatted listing with modification times
 - Parallelize reads when exploring related files
 - Supports internal URLs:
   - `skill://<name>` - read SKILL.md for a skill

package/src/prompts/tools/replace.md

@@ -1,26 +1,26 @@
 # Replace
 
-Performs string replacements in files with fuzzy whitespace matching.
+String replacements in files with fuzzy whitespace matching.
 
 <instruction>
-- Use the smallest edit that uniquely identifies the change
-- If `old_text` is not unique, expand to include more context or use `all: true` to replace all occurrences
+- Use smallest edit that uniquely identifies change
+- If `old_text` not unique, expand to include more context or use `all: true` to replace all occurrences
 - Fuzzy matching handles minor whitespace/indentation differences automatically
 - Prefer editing existing files over creating new ones
 </instruction>
 
 <output>
-Returns success/failure status. On success, the file is modified in place with the replacement applied. On failure (e.g., `old_text` not found or matches multiple locations without `all: true`), returns an error describing the issue.
+Returns success/failure status. On success, file modified in place with replacement applied. On failure (e.g., `old_text` not found or matches multiple locations without `all: true`), returns error describing issue.
 </output>
 
 <critical>
-- You must read the file at least once in the conversation before editing. The tool will error if you attempt an edit without reading the file first.
+- Must read file at least once in conversation before editing. Tool errors if you attempt edit without reading file first.
 </critical>
 
 <bash*alternatives>
-Replace is for content-addressed changes—you identify \_what* to change by its text.
+Replace for content-addressed changes—you identify \_what* to change by its text.
 
-For position-addressed or pattern-addressed changes, bash is more efficient:
+For position-addressed or pattern-addressed changes, bash more efficient:
 
 |Operation|Command|
 |---|---|
@@ -33,6 +33,6 @@ For position-addressed or pattern-addressed changes, bash is more efficient:
 |Copy lines N-M to another file|`sed -n 'N,Mp' src >> dest`|
 |Move lines N-M to another file|`sed -n 'N,Mp' src >> dest && sed -i 'N,Md' src`|
 
-Use Replace when the _content itself_ identifies the location.
+Use Replace when _content itself_ identifies location.
 Use bash when _position_ or _pattern_ identifies what to change.
 </bash_alternatives>

package/src/prompts/tools/ssh.md

@@ -1,64 +1,51 @@
 # SSH
 
-Execute commands on remote SSH hosts.
+Run commands on remote hosts.
 
 <instruction>
-1. Check the host's shell type from "Available hosts" below
-2. Use ONLY commands for that shell type
-3. Construct your command using the reference below
+Build commands from reference below
 </instruction>
 
 <commands>
-**linux/bash, linux/zsh, macos/bash, macos/zsh** — Unix-like systems:
+**linux/bash, linux/zsh, macos/bash, macos/zsh** — Unix-like:
 - Files: `ls`, `cat`, `head`, `tail`, `grep`, `find`
-- System: `ps`, `top`, `df`, `uname`, `free` (Linux), `df`, `uname`, `top` (macOS)
+- System: `ps`, `top`, `df`, `uname` (all), `free` (Linux only)
 - Navigation: `cd`, `pwd`
-**windows/bash, windows/sh** — Windows with Unix compatibility layer (WSL, Cygwin, Git Bash):
-- Files: `ls`, `cat`, `head`, `tail`, `grep`, `find`
-- System: `ps`, `top`, `df`, `uname`
-- Navigation: `cd`, `pwd`
-- Note: These are Windows hosts but use Unix commands
-**windows/powershell** — Native Windows PowerShell:
+**windows/bash, windows/sh** — Windows Unix layer (WSL, Cygwin, Git Bash):
+- Files/System/Navigation: same as Unix-like above, minus `free`
+**windows/powershell** — PowerShell:
 - Files: `Get-ChildItem`, `Get-Content`, `Select-String`
 - System: `Get-Process`, `Get-ComputerInfo`
 - Navigation: `Set-Location`, `Get-Location`
-**windows/cmd** — Native Windows Command Prompt:
+**windows/cmd** — Command Prompt:
 - Files: `dir`, `type`, `findstr`, `where`
 - System: `tasklist`, `systeminfo`
 - Navigation: `cd`, `echo %CD%`
 </commands>
 
 <output>
-Command output (stdout/stderr combined), truncated at 50KB. Exit code is captured.
-If output is truncated, full output is stored under $ARTIFACTS and referenced as `artifact://<id>` in metadata.
+stdout/stderr combined, truncated at 50KB; exit code captured.
+If truncated, full output stored under $ARTIFACTS as `artifact://<id>`.
 </output>
 
 <critical>
-Each host runs a specific shell. You MUST use commands native to that shell.
-Verify host shell type from "Available hosts" and use matching commands.
+Verify shell type from "Available hosts", use matching commands.
 </critical>
 
 <example name="linux">
-Task: List files in /home/user on host "server1"
+Task: List /home/user files on "server1"
 Host: server1 (10.0.0.1) | linux/bash
 Command: `ls -la /home/user`
 </example>
 
 <example name="windows-cmd">
-Task: Show running processes on host "winbox"
+Task: Show running processes on "winbox"
 Host: winbox (192.168.1.5) | windows/cmd
 Command: `tasklist /v`
 </example>
 
-<example name="windows-wsl">
-Task: Check disk usage on host "wsl-dev"
-Host: wsl-dev (192.168.1.10) | windows/bash
-Command: `df -h`
-Note: Windows host with WSL — use Unix commands
-</example>
-
 <example name="macos">
-Task: Get system info on host "macbook"
+Task: Get system info on "macbook"
 Host: macbook (10.0.0.20) | macos/zsh
 Command: `uname -a && sw_vers`
 </example>