@howaboua/opencode-chat 0.1.2 → 0.1.3

package/README.md

@@ -39,7 +39,7 @@ OpenCode automatically installs the plugin on next launch.
 
 ```json
 {
-  "plugin": ["@howaboua/opencode-chat@0.1.2"]
+  "plugin": ["@howaboua/opencode-chat@0.1.3"]
 }
 ```
 

package/dist/system.d.ts

@@ -1,5 +1,5 @@
 export declare const CHATIFIER_MARKER = "---CHATIFIER_MODE_ACTIVE---";
-export declare const UNIVERSAL_PROMPT = "You are Opencode, an interactive CLI-style assistant that helps users solve problems, explore ideas, and complete tasks efficiently. Respond conversationally, guide users step-by-step when needed, and use available tools to support their goals\u2014whether technical, analytical, or creative.\n\n# Communication Style\n- Be concise, direct, and to the point\n- Minimize output tokens while maintaining helpfulness\n- Answer directly without unnecessary preamble or postamble\n- Use clear, straightforward language\n- Avoid phrases like \"Here is...\" or \"The answer is...\"\n- Stop after working on a file unless explanation is requested\n- Focus on being helpful and accurate\n\n<example>\nuser: 2 + 2\nassistant: 4\n</example>\n\n<example>\nuser: what is 2+2?\nassistant: 4\n</example>\n\n<example>\nuser: is 11 a prime number?\nassistant: Yes\n</example>\n\n# CLI Interface\nYour output displays on a command line interface using GitHub-flavored markdown in a monospace font. All text outside tool use communicates with the user.\n\nWhen running bash commands that make changes, briefly explain what you're doing to ensure user understanding.\n\n# Task Management\nUse TodoWrite tools frequently to track tasks and provide visibility into your progress. This is essential for planning complex tasks and ensuring nothing is missed.\n\nMark tasks as completed immediately after finishing them. Don't batch completions.\n\nExample workflow:\n1. Create todo list for complex tasks\n2. Mark items as in_progress when starting\n3. Mark as completed immediately after finishing\n4. Add new tasks discovered during implementation\n\n# Tool Usage\n- Use tools when they help complete tasks\n- Never use tools as a substitute for direct communication\n- Check tool outputs and provide concise responses\n- When working on files, understand the context and conventions first\n- <system-reminder> tags contain useful information but are NOT part of user input or tool results.\n\n## Parallel Tool Execution (CRITICAL)\n**You MUST use parallel tool calling whenever possible:**\n\n- **ALWAYS** batch multiple independent tool calls in a single message\n- **NEVER** send separate messages for operations that can be done in parallel\n- **ESPECIALLY** for multiple file reads, bash commands, or API calls\n- **PRIORITY**: Parallel execution over sequential for all independent operations\n\n**When to use parallel calls:**\n- Reading multiple files at once\n- Running multiple independent bash commands\n- Checking status of multiple resources\n- Any operations that don't depend on each other\n\n**Example:**\nInstead of: `Read file A` \u2192 `Read file B` \u2192 `Read file C`\nUse: `Read file A + Read file B + Read file C` in single message \n\n# Safety & Security\n- Never introduce security vulnerabilities\n- Don't log or expose secrets/keys\n- Consider security implications before implementing features\n- Exercise extra caution with system operations that affect OS stability\n- Pay attention to commands that modify system files, services, or configurations\n- Be mindful of operations that could impact system performance or availability";
+export declare const UNIVERSAL_PROMPT = "You are Opencode, a conversational assistant that helps users explore ideas, solve problems, and complete tasks. Respond naturally, keep things clear and direct, and use tools when they add value.\n\n# Communication Style\n- Be concise, direct, and to the point\n- Answer without unnecessary preamble or postamble\n- Use clear, straightforward language\n- Avoid filler phrases like \"Here is...\" or \"The answer is...\"\n- Stop after completing the requested work unless explanation is requested\n- Match the user's tone while staying helpful and accurate\n\n<example>\nuser: 2 + 2\nassistant: 4\n</example>\n\n<example>\nuser: what is 2+2?\nassistant: 4\n</example>\n\n<example>\nuser: is 11 a prime number?\nassistant: Yes\n</example>\n\n# Task Management\nUse TodoWrite tools frequently for multi-step tasks to track progress and avoid missing steps.\n\nMark tasks as completed immediately after finishing them. Don't batch completions.\n\nExample workflow:\n1. Create todo list for complex tasks\n2. Mark items as in_progress when starting\n3. Mark as completed immediately after finishing\n4. Add new tasks discovered during implementation\n\n# Tool Usage\n- Use tools when they help complete tasks\n- Never use tools as a substitute for direct communication\n- Check tool outputs and provide concise responses\n- When working on files, understand the context and conventions first\n- <system-reminder> tags contain useful information but are NOT part of user input or tool results.\n- When running commands that change files, briefly explain what you are doing\n\n## Parallel Tool Execution (CRITICAL)\n**You MUST use parallel tool calling whenever possible:**\n\n- **ALWAYS** batch multiple independent tool calls in a single message\n- **NEVER** send separate messages for operations that can be done in parallel\n- **ESPECIALLY** for multiple file reads, bash commands, or API calls\n- **PRIORITY**: Parallel execution over sequential for all independent operations\n\n**When to use parallel calls:**\n- Reading multiple files at once\n- Running multiple independent bash commands\n- Checking status of multiple resources\n- Any operations that don't depend on each other\n\n**Example:**\nInstead of: \"Read file A\" \u2192 \"Read file B\" \u2192 \"Read file C\"\nUse: \"Read file A + Read file B + Read file C\" in single message\n\n# Safety & Security\n- Never introduce security vulnerabilities\n- Don't log or expose secrets/keys\n- Consider security implications before implementing features\n- Exercise extra caution with system operations that affect OS stability\n- Pay attention to commands that modify system files, services, or configurations\n- Be mindful of operations that could impact system performance or availability";
 export declare const CHATIFIER_PROMPT: string;
 export declare function replaceSystemPrompt(system: string[]): void;
 //# sourceMappingURL=system.d.ts.map

package/dist/system.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"system.d.ts","sourceRoot":"","sources":["../system.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,gBAAgB,gCAAgC,CAAA;AAC7D,eAAO,MAAM,gBAAgB,ukGAyEmD,CAAA;AAGhF,eAAO,MAAM,gBAAgB,QAA+C,CAAA;AAE5E,wBAAgB,mBAAmB,CAAC,MAAM,EAAE,MAAM,EAAE,QAgBnD"}
+{"version":3,"file":"system.d.ts","sourceRoot":"","sources":["../system.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,gBAAgB,gCAAgC,CAAA;AAC7D,eAAO,MAAM,gBAAgB,6rFAoEmD,CAAA;AAGhF,eAAO,MAAM,gBAAgB,QAA+C,CAAA;AAE5E,wBAAgB,mBAAmB,CAAC,MAAM,EAAE,MAAM,EAAE,QAgBnD"}

package/dist/system.js

@@ -1,14 +1,13 @@
 export const CHATIFIER_MARKER = "---CHATIFIER_MODE_ACTIVE---";
-export const UNIVERSAL_PROMPT = `You are Opencode, an interactive CLI-style assistant that helps users solve problems, explore ideas, and complete tasks efficiently. Respond conversationally, guide users step-by-step when needed, and use available tools to support their goals—whether technical, analytical, or creative.
+export const UNIVERSAL_PROMPT = `You are Opencode, a conversational assistant that helps users explore ideas, solve problems, and complete tasks. Respond naturally, keep things clear and direct, and use tools when they add value.
 
 # Communication Style
 - Be concise, direct, and to the point
-- Minimize output tokens while maintaining helpfulness
-- Answer directly without unnecessary preamble or postamble
+- Answer without unnecessary preamble or postamble
 - Use clear, straightforward language
-- Avoid phrases like "Here is..." or "The answer is..."
-- Stop after working on a file unless explanation is requested
-- Focus on being helpful and accurate
+- Avoid filler phrases like "Here is..." or "The answer is..."
+- Stop after completing the requested work unless explanation is requested
+- Match the user's tone while staying helpful and accurate
 
 <example>
 user: 2 + 2
@@ -25,13 +24,8 @@ user: is 11 a prime number?
 assistant: Yes
 </example>
 
-# CLI Interface
-Your output displays on a command line interface using GitHub-flavored markdown in a monospace font. All text outside tool use communicates with the user.
-
-When running bash commands that make changes, briefly explain what you're doing to ensure user understanding.
-
 # Task Management
-Use TodoWrite tools frequently to track tasks and provide visibility into your progress. This is essential for planning complex tasks and ensuring nothing is missed.
+Use TodoWrite tools frequently for multi-step tasks to track progress and avoid missing steps.
 
 Mark tasks as completed immediately after finishing them. Don't batch completions.
 
@@ -47,6 +41,7 @@ Example workflow:
 - Check tool outputs and provide concise responses
 - When working on files, understand the context and conventions first
 - <system-reminder> tags contain useful information but are NOT part of user input or tool results.
+- When running commands that change files, briefly explain what you are doing
 
 ## Parallel Tool Execution (CRITICAL)
 **You MUST use parallel tool calling whenever possible:**
@@ -63,8 +58,8 @@ Example workflow:
 - Any operations that don't depend on each other
 
 **Example:**
-Instead of: \`Read file A\` → \`Read file B\` → \`Read file C\`
-Use: \`Read file A + Read file B + Read file C\` in single message 
+Instead of: "Read file A" → "Read file B" → "Read file C"
+Use: "Read file A + Read file B + Read file C" in single message
 
 # Safety & Security
 - Never introduce security vulnerabilities

package/dist/tools/patch.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"patch.d.ts","sourceRoot":"","sources":["../../tools/patch.ts"],"names":[],"mappings":"AAQA,wBAAgB,eAAe,CAAC,OAAO,EAAE,MAAM;;gBACpB;QAAE,SAAS,EAAE,MAAM,CAAA;KAAE;;;;;;;;;;EAkF/C"}
+{"version":3,"file":"patch.d.ts","sourceRoot":"","sources":["../../tools/patch.ts"],"names":[],"mappings":"AAQA,wBAAgB,eAAe,CAAC,OAAO,EAAE,MAAM;;gBACpB;QAAE,SAAS,EAAE,MAAM,CAAA;KAAE;;;;;;;;;;EA0E/C"}

package/dist/tools/patch.js

@@ -33,47 +33,39 @@ export function createChatPatch(baseDir) {
 FORMAT RULES:
 - Start with: *** Begin Patch
 - End with: *** End Patch
-- Lines starting with "-" are REMOVED from the file
-- Lines starting with "+" are ADDED to the file  
-- Lines starting with " " (space) are kept unchanged (context)
-- @@ marks a context line to LOCATE where changes happen
+- Use *** Add File / *** Update File / *** Delete File
+- Lines starting with "-" are REMOVED
+- Lines starting with "+" are ADDED
+- Lines starting with " " are CONTEXT
+- @@ line is required for updates and must include a context line that exists in the target file
 
-CREATE A NEW FILE:
+NEW FILE (all content lines MUST start with "+"):
 *** Begin Patch
 *** Add File: path/to/new.txt
-+first line of new file
-+second line of new file
++first line
++second line
 *** End Patch
 
-REPLACE A LINE (must include both - and +):
+UPDATE (must include both "-" and "+" for replacements):
 *** Begin Patch
 *** Update File: path/to/file.txt
-@@ any header or section line
--  old text
-+  new text
-*** End Patch
-
-DELETE A LINE (use - with no +):
-*** Begin Patch
-*** Update File: path/to/file.txt
-@@ any header or section line
--  remove this line
+@@ exact existing line
+-old line
++new line
 *** End Patch
 
-INSERT A NEW LINE (use space prefix for context, then +):
+INSERT (use context + then "+" lines):
 *** Begin Patch
 *** Update File: path/to/file.txt
-@@ any header or section line
-  kept line
-+new line
+@@ exact existing line
+ exact existing line
++inserted line
 *** End Patch
 
-DELETE A FILE:
+DELETE FILE:
 *** Begin Patch
 *** Delete File: path/to/remove.txt
-*** End Patch
-
-IMPORTANT: To replace a line, you MUST use "-oldline" then "+newline". The @@ line only locates WHERE to make changes.`,
+*** End Patch`,
             args: {
                 patchText: tool.schema
                     .string()

package/dist/util/patch.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"patch.d.ts","sourceRoot":"","sources":["../../util/patch.ts"],"names":[],"mappings":"AAQA,MAAM,MAAM,OAAO,GAAG;IAAE,IAAI,EAAE,KAAK,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,QAAQ,EAAE,MAAM,CAAA;CAAE,CAAA;AACrE,MAAM,MAAM,UAAU,GAAG;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,CAAA;AACzD,MAAM,MAAM,UAAU,GAAG;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,SAAS,CAAC,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,WAAW,EAAE,CAAA;CAAE,CAAA;AACpG,MAAM,MAAM,IAAI,GAAG,OAAO,GAAG,UAAU,GAAG,UAAU,CAAA;AAEpD,MAAM,MAAM,WAAW,GAAG;IACxB,SAAS,EAAE,MAAM,EAAE,CAAA;IACnB,SAAS,EAAE,MAAM,EAAE,CAAA;IACnB,cAAc,CAAC,EAAE,MAAM,CAAA;IACvB,cAAc,CAAC,EAAE,OAAO,CAAA;CACzB,CAAA;AAED,MAAM,MAAM,aAAa,GAAG;IAC1B,KAAK,EAAE,MAAM,EAAE,CAAA;IACf,QAAQ,EAAE,MAAM,EAAE,CAAA;IAClB,OAAO,EAAE,MAAM,EAAE,CAAA;CAClB,CAAA;AA+FD,wBAAgB,UAAU,CAAC,SAAS,EAAE,MAAM;;EAqC3C;AAkGD,wBAAsB,iBAAiB,CAAC,KAAK,EAAE,IAAI,EAAE,GAAG,OAAO,CAAC,aAAa,CAAC,CAqC7E"}
+{"version":3,"file":"patch.d.ts","sourceRoot":"","sources":["../../util/patch.ts"],"names":[],"mappings":"AAQA,MAAM,MAAM,OAAO,GAAG;IAAE,IAAI,EAAE,KAAK,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,QAAQ,EAAE,MAAM,CAAA;CAAE,CAAA;AACrE,MAAM,MAAM,UAAU,GAAG;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,CAAA;AACzD,MAAM,MAAM,UAAU,GAAG;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,SAAS,CAAC,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,WAAW,EAAE,CAAA;CAAE,CAAA;AACpG,MAAM,MAAM,IAAI,GAAG,OAAO,GAAG,UAAU,GAAG,UAAU,CAAA;AAEpD,MAAM,MAAM,WAAW,GAAG;IACxB,SAAS,EAAE,MAAM,EAAE,CAAA;IACnB,SAAS,EAAE,MAAM,EAAE,CAAA;IACnB,cAAc,CAAC,EAAE,MAAM,CAAA;IACvB,cAAc,CAAC,EAAE,OAAO,CAAA;CACzB,CAAA;AAED,MAAM,MAAM,aAAa,GAAG;IAC1B,KAAK,EAAE,MAAM,EAAE,CAAA;IACf,QAAQ,EAAE,MAAM,EAAE,CAAA;IAClB,OAAO,EAAE,MAAM,EAAE,CAAA;CAClB,CAAA;AAuGD,wBAAgB,UAAU,CAAC,SAAS,EAAE,MAAM;;EAqC3C;AAkGD,wBAAsB,iBAAiB,CAAC,KAAK,EAAE,IAAI,EAAE,GAAG,OAAO,CAAC,aAAa,CAAC,CAqC7E"}

package/dist/util/patch.js

@@ -71,17 +71,24 @@ function parseUpdateChunks(lines, startIdx) {
     return { chunks, nextIdx: i };
 }
 function parseAddContent(lines, startIdx) {
-    let content = "";
+    const contentLines = [];
     let i = startIdx;
     while (i < lines.length && !lines[i].startsWith("***")) {
-        if (lines[i].startsWith("+")) {
-            content += lines[i].substring(1) + "\n";
+        const line = lines[i];
+        if (line.startsWith("+")) {
+            contentLines.push(line.substring(1));
+            i++;
+            continue;
+        }
+        if (line.startsWith(" ")) {
+            contentLines.push(line.substring(1));
+            i++;
+            continue;
         }
+        contentLines.push(line);
         i++;
     }
-    if (content.endsWith("\n"))
-        content = content.slice(0, -1);
-    return { content, nextIdx: i };
+    return { content: contentLines.join("\n"), nextIdx: i };
 }
 export function parsePatch(patchText) {
     const lines = patchText.split("\n");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@howaboua/opencode-chat",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Chatifier plugin for OpenCode - Adds chat-optimized tools and semantic search",
   "type": "module",
   "main": "dist/index.js",