@oh-my-pi/pi-coding-agent 13.18.0 → 14.0.2

package/src/prompts/tools/debug.md

@@ -0,0 +1,43 @@
+Provides debugger access through the Debug Adapter Protocol (DAP). Use this to launch or attach debuggers, set breakpoints, step through execution, inspect threads/stack/variables, evaluate expressions, capture program output, and interrupt hung programs.
+
+<instruction>
+- Prefer this over bash when you need program state, breakpoints, stepping, thread inspection, or to interrupt a running process.
+- `action: "launch"` starts a debugger session for a program or script. `program` is required. `adapter` is optional; when omitted, the tool selects an installed adapter from the target path and workspace.
+- `action: "attach"` connects to an existing process. Provide `pid` for local process attach or `port` for adapters that support remote attach. Use `adapter` to force a specific debugger.
+- Breakpoints:
+  - Source breakpoints: `set_breakpoint` / `remove_breakpoint` with `file` + `line`
+  - Function breakpoints: `set_breakpoint` / `remove_breakpoint` with `function`
+  - Optional `condition` adds a conditional breakpoint expression
+- Flow control:
+  - `continue` resumes execution and waits briefly to see whether the program stops or keeps running
+  - `step_over`, `step_in`, `step_out` perform single-step execution
+  - `pause` interrupts a running program so you can inspect the current state
+- Inspection:
+  - `threads` lists threads
+  - `stack_trace` returns frames for the current stopped thread
+  - `scopes` requires `frame_id` or a current stopped frame
+  - `variables` requires `variable_ref` or `scope_id`
+  - `evaluate` requires `expression`; use `context: "repl"` for raw debugger commands when the adapter supports them
+  - `output` returns captured stdout/stderr/console output from the debuggee and adapter
+  - `sessions` lists tracked debug sessions
+  - `terminate` ends the active debug session
+- Timeouts apply to individual debugger requests, not the full session lifetime.
+</instruction>
+
+<caution>
+- Only one active debug session is supported at a time.
+- Some adapters require a launched session to receive `configurationDone` before the target actually runs; if the tool says configuration is pending, set breakpoints and then call `continue`.
+- Adapter availability depends on local binaries. Common built-ins are `gdb`, `lldb-dap`, `python -m debugpy.adapter`, and `dlv dap`.
+</caution>
+
+<example name="launch and inspect hang">
+1. `debug(action: "launch", program: "./my_app")`
+2. `debug(action: "set_breakpoint", file: "src/main.c", line: 42)`
+3. `debug(action: "continue")`
+4. If the program appears hung: `debug(action: "pause")`
+5. Inspect state with `threads`, `stack_trace`, `scopes`, and `variables`
+</example>
+
+<example name="raw debugger command through repl">
+`debug(action: "evaluate", expression: "info registers", context: "repl")`
+</example>

package/src/prompts/tools/grep.md

@@ -17,6 +17,9 @@ Searches files using powerful regex matching.
 - Text output is line-number-prefixed
 {{/if}}
 {{/if}}
+{{#if IS_CHUNK_MODE}}
+- Text output is chunk-path-prefixed: `path:selector>LINE|content`
+{{/if}}
 </output>
 
 <critical>

package/src/prompts/tools/lsp.md

@@ -1,21 +1,21 @@
 Interacts with Language Server Protocol servers for code intelligence.
 
 <operations>
-- `diagnostics`: Get errors/warnings for file, glob, or entire workspace (no file)
+- `diagnostics`: Get errors/warnings for a file, a glob of files, or the entire workspace (`file: "*"`)
 - `definition`: Go to symbol definition → file path + position + 3-line source context
 - `type_definition`: Go to symbol type definition → file path + position + 3-line source context
 - `implementation`: Find concrete implementations → file path + position + 3-line source context
 - `references`: Find references → locations with 3-line source context (first 50), remaining location-only
 - `hover`: Get type info and documentation → type signature + docs
-- `symbols`: List symbols in file, or search workspace (with query, no file)
+- `symbols`: List symbols in a file, or search workspace with `file: "*"` and a `query`
 - `rename`: Rename symbol across codebase → preview or apply edits
 - `code_actions`: List available quick-fixes/refactors/import actions; apply one when `apply: true` and `query` matches title or index
 - `status`: Show active language servers
-- `reload`: Restart the language server
+- `reload`: Restart a specific server (via `file`) or all servers with `file: "*"`
 </operations>
 
 <parameters>
-- `file`: File path; for diagnostics it may be a glob pattern (e.g., `src/**/*.ts`)
+- `file`: File path, glob pattern (e.g. `src/**/*.ts`), or `"*"` for workspace scope. Globs are expanded locally before dispatch. `"*"` routes `diagnostics`/`symbols`/`reload` to their workspace-wide form.
 - `line`: 1-indexed line number for position-based actions
 - `symbol`: Substring on the target line used to resolve column automatically
 - `occurrence`: 1-indexed match index when `symbol` appears multiple times on the same line
@@ -28,6 +28,6 @@ Interacts with Language Server Protocol servers for code intelligence.
 <caution>
 - Requires running LSP server for target language
 - Some operations require file to be saved to disk
-- Diagnostics glob mode samples up to 20 files per request to avoid long-running stalls on broad patterns
+- Glob expansion samples up to 20 files per request; use `file: "*"` for broader coverage
 - When `symbol` is provided for position-based actions, missing symbols or out-of-bounds `occurrence` values return an explicit error instead of silently falling back
 </caution>

package/src/prompts/tools/read-chunk.md

@@ -0,0 +1,17 @@
+Reads files using syntax-aware chunks.
+
+<instruction>
+- `path` — file path or URL; may include `:selector` suffix
+- `sel` — optional selector: `class_Foo`, `class_Foo.fn_bar#ABCD@body`, `?`, `L50`, `L50-L120`, or `raw`
+- `timeout` — seconds, for URLs only
+
+Each opening anchor `[< full.chunk.path#CCCC ]` in the default output identifies a chunk. Use `full.chunk.path#CCCC` as-is to read truncated chunks.
+If you need a canonical target list, run `read(path="file", sel="?")`. That listing shows chunk paths with CRCs.
+Line numbers in the gutter are absolute file line numbers.
+
+Chunk trees: JS, TS, TSX, Python, Rust, Go. Others use blank-line fallback.
+</instruction>
+
+<critical>
+- **MUST** `read` before editing — never invent chunk names or CRCs.
+</critical>

package/src/prompts/tools/read.md

@@ -4,9 +4,23 @@ Reads the content at the specified path or URL.
 The `read` tool is a multi-purpose tool that can be used to inspect all kinds of files and URLs.
 - You **MUST** parallelize reads when exploring related files
 
+## Parameters
+- `path` -- file path or URL (required)
+- `sel` -- optional selector for line ranges or raw mode
+- `timeout` -- seconds, for URLs only
+
+## Selectors
+
+|`sel` value|Behavior|
+|---|---|
+|*(omitted)*|Read full file (up to {{DEFAULT_LIMIT}} lines)|
+|`L50`|Read from line 50 onward|
+|`L50-L120`|Read lines 50 through 120|
+|`raw`|Raw content without transformations (for URLs: untouched HTML)|
+
+Max {{DEFAULT_MAX_LINES}} lines per call.
+
 # Filesystem
-- Reads up to {{DEFAULT_LIMIT}} lines by default
-- Use `offset` and `limit` for large files; max {{DEFAULT_MAX_LINES}} lines per call
 {{#if IS_HASHLINE_MODE}}
 - If reading from FS, result will be prefixed with anchors: `41#ZZ:def alpha():`
 {{else}}
@@ -26,7 +40,7 @@ When used against a directory, or an archive root, the tool will return a list o
 
 # URLs
 - Extract information from web pages, GitHub issues/PRs, Stack Overflow, Wikipedia, Reddit, NPM, arXiv, technical blogs, RSS/Atom feeds, JSON endpoints
-- `raw: true` for untouched HTML or debugging
+- `sel="raw"` for untouched HTML or debugging
 - `timeout` to override the default request timeout
 </instruction>
 
@@ -35,6 +49,6 @@ When used against a directory, or an archive root, the tool will return a list o
 - You **MUST** use `read` instead of `ls` for directory listings.
 - You **MUST** use `read` instead of shelling out to `tar` or `unzip` for supported archive reads.
 - You **MUST** always include the `path` parameter, NEVER call `read` with empty arguments `{}`.
-- When reading specific line ranges, use `offset` and `limit`: `read(path="file", offset=50, limit=100)` not `cat -n file | sed`.
-- You **MAY** use `offset` and `limit` with URL reads; the tool will paginate the cached fetched output.
+- When reading specific line ranges, use `sel`: `read(path="file", sel="L50-L150")` not `cat -n file | sed`.
+- You **MAY** use `sel` with URL reads; the tool will paginate the cached fetched output.
 </critical>