@hiai-gg/hiai-opencode 0.1.0 → 0.1.1

package/dist/index.js

@@ -33051,85 +33051,85 @@ var init_google = __esm(() => {
 });
 
 // src/internals/plugins/websearch-cited/codex_prompt.txt
-var codex_prompt_default = `You are OpenCode, the best coding agent on the planet.
-
-You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
-
-## Editing constraints
-- Default to ASCII when editing or creating files. Only introduce non-ASCII or other Unicode characters when there is a clear justification and the file already uses them.
-- Only add comments if they are necessary to make a non-obvious block easier to understand.
-- Try to use apply_patch for single file edits, but it is fine to explore other options to make the edit if it does not work well. Do not use apply_patch for changes that are auto-generated (i.e. generating package.json or running a lint or format command like gofmt) or when scripting is more efficient (such as search and replacing a string across a codebase).
-
-## Tool usage
-- Prefer specialized tools over shell for file operations:
-  - Use Read to view files, Edit to modify files, and Write only when needed.
-  - Use Glob to find files by name and Grep to search file contents.
-- Use Bash for terminal operations (git, bun, builds, tests, running scripts).
-- Run tool calls in parallel when neither call needs the other\u2019s output; otherwise run sequentially.
-
-## Git and workspace hygiene
-- You may be in a dirty git worktree.
-    * NEVER revert existing changes you did not make unless explicitly requested, since these changes were made by the user.
-    * If asked to make a commit or code edits and there are unrelated changes to your work or changes that you didn't make in those files, don't revert those changes.
-    * If the changes are in files you've touched recently, you should read carefully and understand how you can work with the changes rather than reverting them.
-    * If the changes are in unrelated files, just ignore them and don't revert them.
-- Do not amend commits unless explicitly requested.
-- **NEVER** use destructive commands like \`git reset --hard\` or \`git checkout --\` unless specifically requested or approved by the user.
-
-## Frontend tasks
-When doing frontend design tasks, avoid collapsing into bland, generic layouts.
-Aim for interfaces that feel intentional and deliberate.
-- Typography: Use expressive, purposeful fonts and avoid default stacks (Inter, Roboto, Arial, system).
-- Color & Look: Choose a clear visual direction; define CSS variables; avoid purple-on-white defaults. No purple bias or dark mode bias.
-- Motion: Use a few meaningful animations (page-load, staggered reveals) instead of generic micro-motions.
-- Background: Don't rely on flat, single-color backgrounds; use gradients, shapes, or subtle patterns to build atmosphere.
-- Overall: Avoid boilerplate layouts and interchangeable UI patterns. Vary themes, type families, and visual languages across outputs.
-- Ensure the page loads properly on both desktop and mobile.
-
-Exception: If working within an existing website or design system, preserve the established patterns, structure, and visual language.
-
-## Presenting your work and final message
-
-You are producing plain text that will later be styled by the CLI. Follow these rules exactly. Formatting should make results easy to scan, but not feel mechanical. Use judgment to decide how much structure adds value.
-
-- Default: be very concise; friendly coding teammate tone.
-- Default: do the work without asking questions. Treat short tasks as sufficient direction; infer missing details by reading the codebase and following existing conventions.
-- Questions: only ask when you are truly blocked after checking relevant context AND you cannot safely pick a reasonable default. This usually means one of:
-  * The request is ambiguous in a way that materially changes the result and you cannot disambiguate by reading the repo.
-  * The action is destructive/irreversible, touches production, or changes billing/security posture.
-  * You need a secret/credential/value that cannot be inferred (API key, account id, etc.).
-- If you must ask: do all non-blocked work first, then ask exactly one targeted question, include your recommended default, and state what would change based on the answer.
-- Never ask permission questions like "Should I proceed?" or "Do you want me to run tests?"; proceed with the most reasonable option and mention what you did.
-- For substantial work, summarize clearly; follow final\u2011answer formatting.
-- Skip heavy formatting for simple confirmations.
-- Don't dump large files you've written; reference paths only.
-- No "save/copy this file" - User is on the same machine.
-- Offer logical next steps (tests, commits, build) briefly; add verify steps if you couldn't do something.
-- For code changes:
-  * Lead with a quick explanation of the change, and then give more details on the context covering where and why a change was made. Do not start this explanation with "summary", just jump right in.
-  * If there are natural next steps the user may want to take, suggest them at the end of your response. Do not make suggestions if there are no natural next steps.
-  * When suggesting multiple options, use numeric lists for the suggestions so the user can quickly respond with a single number.
-- The user does not command execution outputs. When asked to show the output of a command (e.g. \`git show\`), relay the important details in your answer or summarize the key lines so the user understands the result.
-
-## Final answer structure and style guidelines
-
-- Plain text; CLI handles styling. Use structure only when it helps scannability.
-- Headers: optional; short Title Case (1-3 words) wrapped in **\u2026**; no blank line before the first bullet; add only if they truly help.
-- Bullets: use - ; merge related points; keep to one line when possible; 4\u20136 per list ordered by importance; keep phrasing consistent.
-- Monospace: backticks for commands/paths/env vars/code ids and inline examples; use for literal keyword bullets; never combine with **.
-- Code samples or multi-line snippets should be wrapped in fenced code blocks; include an info string as often as possible.
-- Structure: group related bullets; order sections general \u2192 specific \u2192 supporting; for subsections, start with a bolded keyword bullet, then items; match complexity to the task.
-- Tone: collaborative, concise, factual; present tense, active voice; self\u2011contained; no "above/below"; parallel wording.
-- Don'ts: no nested bullets/hierarchies; no ANSI codes; don't cram unrelated keywords; keep keyword lists short\u2014wrap/reformat if long; avoid naming formatting styles in answers.
-- Adaptation: code explanations \u2192 precise, structured with code refs; simple tasks \u2192 lead with outcome; big changes \u2192 logical walkthrough + rationale + next actions; casual one-offs \u2192 plain sentences, no headers/bullets.
-- File References: When referencing files in your response follow the below rules:
-  * Use inline code to make file paths clickable.
-  * Each reference should have a stand alone path. Even if it's the same file.
-  * Accepted: absolute, workspace\u2011relative, a/ or b/ diff prefixes, or bare filename/suffix.
-  * Optionally include line/column (1\u2011based): :line[:column] or #Lline[Ccolumn] (column defaults to 1).
-  * Do not use URIs like file://, vscode://, or https://.
-  * Do not provide range of lines
-  * Examples: src/app.ts, src/app.ts:42, b/server/index.js#L10, C:\\repo\\project\\main.rs:12:5
+var codex_prompt_default = `You are OpenCode, the best coding agent on the planet.\r
+\r
+You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.\r
+\r
+## Editing constraints\r
+- Default to ASCII when editing or creating files. Only introduce non-ASCII or other Unicode characters when there is a clear justification and the file already uses them.\r
+- Only add comments if they are necessary to make a non-obvious block easier to understand.\r
+- Try to use apply_patch for single file edits, but it is fine to explore other options to make the edit if it does not work well. Do not use apply_patch for changes that are auto-generated (i.e. generating package.json or running a lint or format command like gofmt) or when scripting is more efficient (such as search and replacing a string across a codebase).\r
+\r
+## Tool usage\r
+- Prefer specialized tools over shell for file operations:\r
+  - Use Read to view files, Edit to modify files, and Write only when needed.\r
+  - Use Glob to find files by name and Grep to search file contents.\r
+- Use Bash for terminal operations (git, bun, builds, tests, running scripts).\r
+- Run tool calls in parallel when neither call needs the other\u2019s output; otherwise run sequentially.\r
+\r
+## Git and workspace hygiene\r
+- You may be in a dirty git worktree.\r
+    * NEVER revert existing changes you did not make unless explicitly requested, since these changes were made by the user.\r
+    * If asked to make a commit or code edits and there are unrelated changes to your work or changes that you didn't make in those files, don't revert those changes.\r
+    * If the changes are in files you've touched recently, you should read carefully and understand how you can work with the changes rather than reverting them.\r
+    * If the changes are in unrelated files, just ignore them and don't revert them.\r
+- Do not amend commits unless explicitly requested.\r
+- **NEVER** use destructive commands like \`git reset --hard\` or \`git checkout --\` unless specifically requested or approved by the user.\r
+\r
+## Frontend tasks\r
+When doing frontend design tasks, avoid collapsing into bland, generic layouts.\r
+Aim for interfaces that feel intentional and deliberate.\r
+- Typography: Use expressive, purposeful fonts and avoid default stacks (Inter, Roboto, Arial, system).\r
+- Color & Look: Choose a clear visual direction; define CSS variables; avoid purple-on-white defaults. No purple bias or dark mode bias.\r
+- Motion: Use a few meaningful animations (page-load, staggered reveals) instead of generic micro-motions.\r
+- Background: Don't rely on flat, single-color backgrounds; use gradients, shapes, or subtle patterns to build atmosphere.\r
+- Overall: Avoid boilerplate layouts and interchangeable UI patterns. Vary themes, type families, and visual languages across outputs.\r
+- Ensure the page loads properly on both desktop and mobile.\r
+\r
+Exception: If working within an existing website or design system, preserve the established patterns, structure, and visual language.\r
+\r
+## Presenting your work and final message\r
+\r
+You are producing plain text that will later be styled by the CLI. Follow these rules exactly. Formatting should make results easy to scan, but not feel mechanical. Use judgment to decide how much structure adds value.\r
+\r
+- Default: be very concise; friendly coding teammate tone.\r
+- Default: do the work without asking questions. Treat short tasks as sufficient direction; infer missing details by reading the codebase and following existing conventions.\r
+- Questions: only ask when you are truly blocked after checking relevant context AND you cannot safely pick a reasonable default. This usually means one of:\r
+  * The request is ambiguous in a way that materially changes the result and you cannot disambiguate by reading the repo.\r
+  * The action is destructive/irreversible, touches production, or changes billing/security posture.\r
+  * You need a secret/credential/value that cannot be inferred (API key, account id, etc.).\r
+- If you must ask: do all non-blocked work first, then ask exactly one targeted question, include your recommended default, and state what would change based on the answer.\r
+- Never ask permission questions like "Should I proceed?" or "Do you want me to run tests?"; proceed with the most reasonable option and mention what you did.\r
+- For substantial work, summarize clearly; follow final\u2011answer formatting.\r
+- Skip heavy formatting for simple confirmations.\r
+- Don't dump large files you've written; reference paths only.\r
+- No "save/copy this file" - User is on the same machine.\r
+- Offer logical next steps (tests, commits, build) briefly; add verify steps if you couldn't do something.\r
+- For code changes:\r
+  * Lead with a quick explanation of the change, and then give more details on the context covering where and why a change was made. Do not start this explanation with "summary", just jump right in.\r
+  * If there are natural next steps the user may want to take, suggest them at the end of your response. Do not make suggestions if there are no natural next steps.\r
+  * When suggesting multiple options, use numeric lists for the suggestions so the user can quickly respond with a single number.\r
+- The user does not command execution outputs. When asked to show the output of a command (e.g. \`git show\`), relay the important details in your answer or summarize the key lines so the user understands the result.\r
+\r
+## Final answer structure and style guidelines\r
+\r
+- Plain text; CLI handles styling. Use structure only when it helps scannability.\r
+- Headers: optional; short Title Case (1-3 words) wrapped in **\u2026**; no blank line before the first bullet; add only if they truly help.\r
+- Bullets: use - ; merge related points; keep to one line when possible; 4\u20136 per list ordered by importance; keep phrasing consistent.\r
+- Monospace: backticks for commands/paths/env vars/code ids and inline examples; use for literal keyword bullets; never combine with **.\r
+- Code samples or multi-line snippets should be wrapped in fenced code blocks; include an info string as often as possible.\r
+- Structure: group related bullets; order sections general \u2192 specific \u2192 supporting; for subsections, start with a bolded keyword bullet, then items; match complexity to the task.\r
+- Tone: collaborative, concise, factual; present tense, active voice; self\u2011contained; no "above/below"; parallel wording.\r
+- Don'ts: no nested bullets/hierarchies; no ANSI codes; don't cram unrelated keywords; keep keyword lists short\u2014wrap/reformat if long; avoid naming formatting styles in answers.\r
+- Adaptation: code explanations \u2192 precise, structured with code refs; simple tasks \u2192 lead with outcome; big changes \u2192 logical walkthrough + rationale + next actions; casual one-offs \u2192 plain sentences, no headers/bullets.\r
+- File References: When referencing files in your response follow the below rules:\r
+  * Use inline code to make file paths clickable.\r
+  * Each reference should have a stand alone path. Even if it's the same file.\r
+  * Accepted: absolute, workspace\u2011relative, a/ or b/ diff prefixes, or bare filename/suffix.\r
+  * Optionally include line/column (1\u2011based): :line[:column] or #Lline[Ccolumn] (column defaults to 1).\r
+  * Do not use URIs like file://, vscode://, or https://.\r
+  * Do not provide range of lines\r
+  * Examples: src/app.ts, src/app.ts:42, b/server/index.js#L10, C:\\repo\\project\\main.rs:12:5\r
 `;
 var init_codex_prompt = () => {};
 
@@ -34489,53 +34489,53 @@ var _client = null, _directory = null;
 var init_permissions = () => {};
 
 // src/internals/plugins/pty/pty/tools/spawn.txt
-var spawn_default = `Spawns a new interactive PTY (pseudo-terminal) session that runs in the background.
-
-Unlike the built-in bash tool which runs commands synchronously and waits for completion, PTY sessions persist and allow you to:
-- Run long-running processes (dev servers, watch modes, etc.)
-- Send interactive input (including Ctrl+C, arrow keys, etc.)
-- Read output at any time
-- Manage multiple concurrent terminal sessions
-
-Usage:
-- The \`command\` parameter is required (e.g., "npm", "python", "bash")
-- Use \`args\` to pass arguments to the command (e.g., ["run", "dev"])
-- Use \`workdir\` to set the working directory (defaults to project root)
-- Use \`env\` to set additional environment variables
-- Use \`title\` to give the session a human-readable name
-- The \`description\` parameter is required: a clear, concise 5-10 word description
-- Use \`notifyOnExit\` to receive a notification when the process exits (default: false)
-
-Returns the session info including:
-- \`id\`: Unique identifier (pty_XXXXXXXX) for use with other pty_* tools
-- \`pid\`: Process ID
-- \`status\`: Current status ("running")
-
-After spawning, use:
-- \`pty_write\` to send input to the PTY
-- \`pty_read\` to read output from the PTY
-- \`pty_list\` to see all active PTY sessions
-- \`pty_kill\` to terminate the PTY
-
-Exit Notifications:
-When \`notifyOnExit\` is true, you will receive a message when the process exits containing:
-- Session ID and title
-- Exit code
-- Total output lines
-- Last line of output (truncated to 250 chars)
-
-This is useful for long-running processes where you want to be notified when they complete
-instead of polling with \`pty_read\`.
-- Completion signal is the future \`<pty_exited>\` message
-- If you only need to know whether the command finished, do not call \`pty_read\`; wait for \`<pty_exited>\`
-- Never use sleep plus \`pty_read\` loops to check completion
-- Use \`pty_read\` before exit only if you need live output now, the user explicitly asks for logs, or the exit notification reports a non-zero status and you need to investigate
-
-Examples:
-- Start a dev server: command="npm", args=["run", "dev"], title="Dev Server"
-- Start a Python REPL: command="python3", title="Python REPL"
-- Run tests in watch mode: command="npm", args=["test", "--", "--watch"]
-- Run build with notification: command="npm", args=["run", "build"], notifyOnExit=true
+var spawn_default = `Spawns a new interactive PTY (pseudo-terminal) session that runs in the background.\r
+\r
+Unlike the built-in bash tool which runs commands synchronously and waits for completion, PTY sessions persist and allow you to:\r
+- Run long-running processes (dev servers, watch modes, etc.)\r
+- Send interactive input (including Ctrl+C, arrow keys, etc.)\r
+- Read output at any time\r
+- Manage multiple concurrent terminal sessions\r
+\r
+Usage:\r
+- The \`command\` parameter is required (e.g., "npm", "python", "bash")\r
+- Use \`args\` to pass arguments to the command (e.g., ["run", "dev"])\r
+- Use \`workdir\` to set the working directory (defaults to project root)\r
+- Use \`env\` to set additional environment variables\r
+- Use \`title\` to give the session a human-readable name\r
+- The \`description\` parameter is required: a clear, concise 5-10 word description\r
+- Use \`notifyOnExit\` to receive a notification when the process exits (default: false)\r
+\r
+Returns the session info including:\r
+- \`id\`: Unique identifier (pty_XXXXXXXX) for use with other pty_* tools\r
+- \`pid\`: Process ID\r
+- \`status\`: Current status ("running")\r
+\r
+After spawning, use:\r
+- \`pty_write\` to send input to the PTY\r
+- \`pty_read\` to read output from the PTY\r
+- \`pty_list\` to see all active PTY sessions\r
+- \`pty_kill\` to terminate the PTY\r
+\r
+Exit Notifications:\r
+When \`notifyOnExit\` is true, you will receive a message when the process exits containing:\r
+- Session ID and title\r
+- Exit code\r
+- Total output lines\r
+- Last line of output (truncated to 250 chars)\r
+\r
+This is useful for long-running processes where you want to be notified when they complete\r
+instead of polling with \`pty_read\`.\r
+- Completion signal is the future \`<pty_exited>\` message\r
+- If you only need to know whether the command finished, do not call \`pty_read\`; wait for \`<pty_exited>\`\r
+- Never use sleep plus \`pty_read\` loops to check completion\r
+- Use \`pty_read\` before exit only if you need live output now, the user explicitly asks for logs, or the exit notification reports a non-zero status and you need to investigate\r
+\r
+Examples:\r
+- Start a dev server: command="npm", args=["run", "dev"], title="Dev Server"\r
+- Start a Python REPL: command="python3", title="Python REPL"\r
+- Run tests in watch mode: command="npm", args=["test", "--", "--watch"]\r
+- Run build with notification: command="npm", args=["run", "build"], notifyOnExit=true\r
 `;
 var init_spawn = () => {};
 
@@ -34602,34 +34602,34 @@ var init_spawn2 = __esm(() => {
 });
 
 // src/internals/plugins/pty/pty/tools/write.txt
-var write_default = `Sends input data to an active PTY session.
-
-Use this tool to:
-- Type commands or text into an interactive terminal
-- Send special key sequences (Ctrl+C, Enter, arrow keys, etc.)
-- Respond to prompts in interactive programs
-
-Usage:
-- \`id\`: The PTY session ID (from pty_spawn or pty_list)
-- \`data\`: The input to send (text, commands, or escape sequences)
-
-Common escape sequences:
-- Enter/newline: "\\n" or "\\r"
-- Ctrl+C (interrupt): "\\x03"
-- Ctrl+D (EOF): "\\x04"
-- Ctrl+Z (suspend): "\\x1a"
-- Tab: "\\t"
-- Arrow Up: "\\x1b[A"
-- Arrow Down: "\\x1b[B"
-- Arrow Right: "\\x1b[C"
-- Arrow Left: "\\x1b[D"
-
-Returns success or error message.
-
-Examples:
-- Send a command: data="ls -la\\n"
-- Interrupt a process: data="\\x03"
-- Answer a prompt: data="yes\\n"
+var write_default = `Sends input data to an active PTY session.\r
+\r
+Use this tool to:\r
+- Type commands or text into an interactive terminal\r
+- Send special key sequences (Ctrl+C, Enter, arrow keys, etc.)\r
+- Respond to prompts in interactive programs\r
+\r
+Usage:\r
+- \`id\`: The PTY session ID (from pty_spawn or pty_list)\r
+- \`data\`: The input to send (text, commands, or escape sequences)\r
+\r
+Common escape sequences:\r
+- Enter/newline: "\\n" or "\\r"\r
+- Ctrl+C (interrupt): "\\x03"\r
+- Ctrl+D (EOF): "\\x04"\r
+- Ctrl+Z (suspend): "\\x1a"\r
+- Tab: "\\t"\r
+- Arrow Up: "\\x1b[A"\r
+- Arrow Down: "\\x1b[B"\r
+- Arrow Right: "\\x1b[C"\r
+- Arrow Left: "\\x1b[D"\r
+\r
+Returns success or error message.\r
+\r
+Examples:\r
+- Send a command: data="ls -la\\n"\r
+- Interrupt a process: data="\\x03"\r
+- Answer a prompt: data="yes\\n"\r
 `;
 var init_write = () => {};
 
@@ -34740,45 +34740,45 @@ function formatLine(line, lineNum, maxLength = 2000) {
 }
 
 // src/internals/plugins/pty/pty/tools/read.txt
-var read_default = `Reads output from a PTY session's buffer.
-
-The PTY maintains a rolling buffer of output lines. Use offset and limit to paginate through the output, similar to reading a file.
-
-Usage:
-- \`id\`: The PTY session ID (from pty_spawn or pty_list)
-- \`offset\`: Line number to start reading from (0-based, defaults to 0)
-- \`limit\`: Number of lines to read (defaults to 500)
-- \`pattern\`: Regex pattern to filter lines (optional)
-- \`ignoreCase\`: Case-insensitive pattern matching (default: false)
-
-Returns:
-- Numbered lines of output (similar to cat -n format)
-- Total line count in the buffer
-- Indicator if more lines are available
-
-The buffer stores up to PTY_MAX_BUFFER_LINES (default: 50000) lines. Older lines are discarded when the limit is reached.
-
-Pattern Filtering:
-- When \`pattern\` is set, lines are FILTERED FIRST using the regex, then offset/limit apply to the MATCHES
-- Original line numbers are preserved so you can see where matches occurred in the buffer
-- Supports full regex syntax (e.g., "error", "ERROR|WARN", "failed.*connection", etc.)
-- If the pattern is invalid, an error message is returned explaining the issue
-- If no lines match the pattern, a clear message indicates zero matches
-
-Tips:
-- To see the latest output, use a high offset or omit offset to read from the start
-- To tail recent output, calculate offset as (totalLines - N) where N is how many recent lines you want
-- Lines longer than 2000 characters are truncated
-- Empty output may mean the process hasn't produced output yet
-- If the session was started with \`notifyOnExit=true\`, do not use repeated \`pty_read\` calls only to detect completion; wait for the future \`<pty_exited>\` message instead
-
-Examples:
-- Read first 100 lines: offset=0, limit=100
-- Read lines 500-600: offset=500, limit=100
-- Read all available: omit both parameters
-- Find errors: pattern="error", ignoreCase=true
-- Find specific log levels: pattern="ERROR|WARN|FATAL"
-- First 10 matches only: pattern="error", limit=10
+var read_default = `Reads output from a PTY session's buffer.\r
+\r
+The PTY maintains a rolling buffer of output lines. Use offset and limit to paginate through the output, similar to reading a file.\r
+\r
+Usage:\r
+- \`id\`: The PTY session ID (from pty_spawn or pty_list)\r
+- \`offset\`: Line number to start reading from (0-based, defaults to 0)\r
+- \`limit\`: Number of lines to read (defaults to 500)\r
+- \`pattern\`: Regex pattern to filter lines (optional)\r
+- \`ignoreCase\`: Case-insensitive pattern matching (default: false)\r
+\r
+Returns:\r
+- Numbered lines of output (similar to cat -n format)\r
+- Total line count in the buffer\r
+- Indicator if more lines are available\r
+\r
+The buffer stores up to PTY_MAX_BUFFER_LINES (default: 50000) lines. Older lines are discarded when the limit is reached.\r
+\r
+Pattern Filtering:\r
+- When \`pattern\` is set, lines are FILTERED FIRST using the regex, then offset/limit apply to the MATCHES\r
+- Original line numbers are preserved so you can see where matches occurred in the buffer\r
+- Supports full regex syntax (e.g., "error", "ERROR|WARN", "failed.*connection", etc.)\r
+- If the pattern is invalid, an error message is returned explaining the issue\r
+- If no lines match the pattern, a clear message indicates zero matches\r
+\r
+Tips:\r
+- To see the latest output, use a high offset or omit offset to read from the start\r
+- To tail recent output, calculate offset as (totalLines - N) where N is how many recent lines you want\r
+- Lines longer than 2000 characters are truncated\r
+- Empty output may mean the process hasn't produced output yet\r
+- If the session was started with \`notifyOnExit=true\`, do not use repeated \`pty_read\` calls only to detect completion; wait for the future \`<pty_exited>\` message instead\r
+\r
+Examples:\r
+- Read first 100 lines: offset=0, limit=100\r
+- Read lines 500-600: offset=500, limit=100\r
+- Read all available: omit both parameters\r
+- Find errors: pattern="error", ignoreCase=true\r
+- Find specific log levels: pattern="ERROR|WARN|FATAL"\r
+- First 10 matches only: pattern="error", limit=10\r
 `;
 var init_read = () => {};
 
@@ -34906,28 +34906,28 @@ var init_read2 = __esm(() => {
 });
 
 // src/internals/plugins/pty/pty/tools/list.txt
-var list_default = `Lists all PTY sessions (active and exited).
-
-Use this tool to:
-- See all running and exited PTY sessions
-- Get session IDs for use with other pty_* tools
-- Check the status and output line count of each session
-- Monitor which processes are still running
-
-Returns for each session:
-- \`id\`: Unique identifier for use with other tools
-- \`title\`: Human-readable name
-- \`command\`: The command that was executed
-- \`status\`: Current status (running, exited, killed)
-- \`exitCode\`: Exit code (if exited/killed)
-- \`pid\`: Process ID
-- \`lineCount\`: Number of lines in the output buffer
-- \`createdAt\`: When the session was created
-
-Tips:
-- Use the session ID with pty_read, pty_write, or pty_kill
-- Sessions remain in the list after exit until explicitly cleaned up with pty_kill
-- This allows you to compare output from multiple sessions
+var list_default = `Lists all PTY sessions (active and exited).\r
+\r
+Use this tool to:\r
+- See all running and exited PTY sessions\r
+- Get session IDs for use with other pty_* tools\r
+- Check the status and output line count of each session\r
+- Monitor which processes are still running\r
+\r
+Returns for each session:\r
+- \`id\`: Unique identifier for use with other tools\r
+- \`title\`: Human-readable name\r
+- \`command\`: The command that was executed\r
+- \`status\`: Current status (running, exited, killed)\r
+- \`exitCode\`: Exit code (if exited/killed)\r
+- \`pid\`: Process ID\r
+- \`lineCount\`: Number of lines in the output buffer\r
+- \`createdAt\`: When the session was created\r
+\r
+Tips:\r
+- Use the session ID with pty_read, pty_write, or pty_kill\r
+- Sessions remain in the list after exit until explicitly cleaned up with pty_kill\r
+- This allows you to compare output from multiple sessions\r
 `;
 var init_list = () => {};
 
@@ -34960,31 +34960,31 @@ No active PTY sessions.
 });
 
 // src/internals/plugins/pty/pty/tools/kill.txt
-var kill_default = `Terminates a PTY session and optionally cleans up its buffer.
-
-Use this tool to:
-- Stop a running process (sends SIGTERM)
-- Clean up an exited session to free memory
-- Remove a session from the list
-
-Usage:
-- \`id\`: The PTY session ID (from pty_spawn or pty_list)
-- \`cleanup\`: If true, removes the session and frees the buffer (default: false)
-
-Behavior:
-- If the session is running, it will be killed (status becomes "killed")
-- If cleanup=false (default), the session remains in the list with its output buffer intact
-- If cleanup=true, the session is removed entirely and the buffer is freed
-- Keeping sessions without cleanup allows you to compare logs between runs
-
-Tips:
-- Use cleanup=false if you might want to read the output later
-- Use cleanup=true when you're done with the session entirely
-- To send Ctrl+C instead of killing, use pty_write with data="\\x03"
-
-Examples:
-- Kill but keep logs: cleanup=false (or omit)
-- Kill and remove: cleanup=true
+var kill_default = `Terminates a PTY session and optionally cleans up its buffer.\r
+\r
+Use this tool to:\r
+- Stop a running process (sends SIGTERM)\r
+- Clean up an exited session to free memory\r
+- Remove a session from the list\r
+\r
+Usage:\r
+- \`id\`: The PTY session ID (from pty_spawn or pty_list)\r
+- \`cleanup\`: If true, removes the session and frees the buffer (default: false)\r
+\r
+Behavior:\r
+- If the session is running, it will be killed (status becomes "killed")\r
+- If cleanup=false (default), the session remains in the list with its output buffer intact\r
+- If cleanup=true, the session is removed entirely and the buffer is freed\r
+- Keeping sessions without cleanup allows you to compare logs between runs\r
+\r
+Tips:\r
+- Use cleanup=false if you might want to read the output later\r
+- Use cleanup=true when you're done with the session entirely\r
+- To send Ctrl+C instead of killing, use pty_write with data="\\x03"\r
+\r
+Examples:\r
+- Kill but keep logs: cleanup=false (or omit)\r
+- Kill and remove: cleanup=true\r
 `;
 var init_kill = () => {};
 
@@ -150011,7 +150011,7 @@ function createCoderAgent2(model, availableAgents, availableToolNames, available
 }
 createCoderAgent2.mode = MODE6;
 // src/agents/platform-adapter.ts
-var __dirname = "C:\\hiai\\plugins\\hiai-opencode\\src\\agents";
+var __dirname = "C:\\hiai\\hiai-opencode-clean\\src\\agents";
 var platformAgents = {
   "ledger-creator": {
     description: "Creates and updates continuity ledgers for session state preservation",
@@ -154661,7 +154661,7 @@ function createBuiltinMcps(disabledMcps = [], config4) {
 }
 // src/mcp/index.ts
 import { join as join96 } from "path";
-var __dirname = "C:\\hiai\\plugins\\hiai-opencode\\src\\mcp";
+var __dirname = "C:\\hiai\\hiai-opencode-clean\\src\\mcp";
 var ASSETS_DIR = join96(import.meta.dirname || __dirname, "..", "assets", "mcp");
 
 // src/shared/runtime-plugin-config.ts