@agi-cli/sdk 0.1.80 → 0.1.81

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@agi-cli/sdk",
-	"version": "0.1.80",
+	"version": "0.1.81",
 	"description": "AI agent SDK for building intelligent assistants - tree-shakable and comprehensive",
 	"author": "ntishxyz",
 	"license": "MIT",

package/src/core/src/tools/builtin/fs/write.txt

@@ -4,7 +4,8 @@
 - Returns a compact patch artifact summarizing the change
 
 Usage tips:
-- Only use for creating new files or completely replacing file content
+- Use for creating NEW files
+- Use when replacing >70% of a file's content (almost complete rewrite)
 - NEVER use for partial/targeted edits - use apply_patch or edit instead
 - Using write for partial edits wastes output tokens and risks hallucinating unchanged parts
 - Prefer idempotent writes by providing the full intended content when you do use write

package/src/core/src/tools/builtin/patch.ts

@@ -351,7 +351,9 @@ function parseEnvelopedPatch(patch: string): ParsedPatchOperation[] {
 		} else if (prefix === ' ') {
 			currentHunk.lines.push({ kind: 'context', content: line.slice(1) });
 		} else {
-			throw new Error(`Unrecognized patch line: "${line}"`);
+			// Auto-correct: treat lines without prefix as context (with implicit space)
+			// This makes the parser more forgiving for AI-generated patches
+			currentHunk.lines.push({ kind: 'context', content: line });
 		}
 	}
 

package/src/core/src/tools/builtin/patch.txt

@@ -60,7 +60,7 @@ All patches must be wrapped in markers and use explicit file directives:
 ```
 *** Begin Patch
 *** Update File: src/app.ts
-@@ function main() - locates the change position
+@@ function main()
  function main() {
 -  console.log("old");
 +  console.log("new");
@@ -68,9 +68,33 @@ All patches must be wrapped in markers and use explicit file directives:
 *** End Patch
 ```
 
-**IMPORTANT**: The `@@ context line` is a hint for finding the location - it's NOT a line from the file.
-It should describe what to look for (e.g., `@@ inside main function` or `@@ config section`).
-The actual context lines (with leading space) come AFTER the `@@` line.
+**IMPORTANT**: 
+- The `@@` line is an OPTIONAL hint to help locate the change - it's a comment, not parsed as context
+- REQUIRED: Actual context lines (starting with space ` `) that match the file exactly
+- The context lines with space prefix are what the tool uses to find the location
+- The `@@` line just helps humans/AI understand what section you're editing
+
+
+### Update multiple locations in the same file:
+```
+*** Begin Patch
+*** Update File: src/app.ts
+@@ first section - near line 10
+ function init() {
+-  const port = 3000;
++  const port = 8080;
+   return port;
+ }
+@@ second section - near line 25
+ function start() {
+-  console.log("Starting...");
++  console.log("Server starting...");
+   init();
+ }
+*** End Patch
+```
+
+**IMPORTANT**: Use separate `@@` headers for each non-consecutive change location. This allows multiple edits to the same file in one patch, saving tokens and reducing tool calls.
 
 ### Delete a file:
 ```
@@ -96,11 +120,17 @@ The actual context lines (with leading space) come AFTER the `@@` line.
 - Lines starting with `+` are added
 - Lines starting with `-` are removed  
 - Lines starting with ` ` (space) are context (kept unchanged)
-- Lines starting with `@@` provide context for finding the location
+- Lines starting with `@@` are optional hints/comments (not parsed as context)
 
 ## Common Errors
 
-**"Failed to find expected lines"**: The file content doesn't match your patch. The file may have changed, or you may have mistyped the lines. Solution: Use the `edit` tool instead.
+**"Failed to find expected lines"**: The file content doesn't match your patch. Common causes:
+- Missing context lines (lines with space prefix)
+- Using `@@` line as context instead of real context lines
+- The file content has changed since you read it
+- Whitespace/indentation mismatch
+
+**Solution**: Always read the file immediately before patching and include actual context lines with space prefix.
 
 ## Important Notes
 

package/src/prompts/src/providers/anthropic.txt

@@ -87,9 +87,23 @@ When making changes to files, first understand the file's code conventions. Mimi
 - Primary choice for targeted file edits - avoids rewriting entire files
 - Only requires the specific lines you want to change
 - Format: `*** Begin Patch` ... `*** Update File: path` ... `-old` / `+new` ... `*** End Patch`
+- For multiple changes in one file: use multiple `@@` headers to separate non-consecutive hunks
+- MUST include context lines (space prefix) - the `@@` line is just an optional hint
 - Workflow: 1) Read file, 2) Create patch based on what you just read, 3) Apply patch
 - The `-` lines in your patch MUST match exactly what's in the file character-for-character
 - If patch fails, it means the file content doesn't match - read it again and retry
+- **Best for**: Small, surgical edits to code files (< 50 line changes per file)
+- **Struggles with**: Large restructures (> 50 lines), major section reorganizations
+
+**Patch Format Reminder**:
+```
+*** Update File: path
+@@ optional hint              ← Optional comment/hint (not parsed)
+ actual line from file        ← Context (space prefix) - REQUIRED
+-line to remove               ← Remove this line
++line to add                  ← Add this line
+ more context                 ← More context (space prefix)
+```
 
 **Using the `edit` Tool** (Alternative):
 - Specify the file path and a list of operations
@@ -99,13 +113,14 @@ When making changes to files, first understand the file's code conventions. Mimi
 - When making multiple changes to a file, use ONE `edit` call with multiple ops
 
 **Using the `write` Tool** (Last Resort):
-- Only use when creating new files or completely replacing file content
+- Use for creating NEW files
+- Use when replacing >70% of a file's content (almost complete rewrite)
 - NEVER use for targeted edits - it rewrites the entire file
 - Wastes output tokens and risks hallucinating unchanged parts
 
 **Never**:
 - Use `write` for partial file edits (use `apply_patch` or `edit` instead)
-- Make multiple separate `edit` or `apply_patch` calls for the same file
+- Make multiple separate `edit` or `apply_patch` calls for the same file (use multiple hunks with @@ headers or multiple ops instead)
 - Assume file content remains unchanged between operations
 - Use `bash` with `sed`/`awk` for programmatic file editing (use `edit` instead)
 

package/src/prompts/src/providers/default.txt

@@ -51,9 +51,23 @@ You have access to a rich set of specialized tools optimized for coding tasks:
 - Primary choice for targeted file edits - avoids rewriting entire files
 - Only requires the specific lines you want to change
 - Format: `*** Begin Patch` ... `*** Update File: path` ... `-old` / `+new` ... `*** End Patch`
+- For multiple changes in one file: use multiple `@@` headers to separate non-consecutive hunks
+- MUST include context lines (space prefix) - the `@@` line is just an optional hint
 - Workflow: 1) Read file, 2) Create patch based on what you just read, 3) Apply patch
 - The `-` lines in your patch MUST match exactly what's in the file character-for-character
 - If patch fails, it means the file content doesn't match - read it again and retry
+- **Best for**: Small, surgical edits to code files (< 50 line changes per file)
+- **Struggles with**: Large restructures (> 50 lines), major section reorganizations
+
+**Patch Format Reminder**:
+```
+*** Update File: path
+@@ optional hint              ← Optional comment/hint (not parsed)
+ actual line from file        ← Context (space prefix) - REQUIRED
+-line to remove               ← Remove this line
++line to add                  ← Add this line
+ more context                 ← More context (space prefix)
+```
 
 **Using the `edit` Tool** (Alternative):
 - Specify the file path and a list of operations
@@ -63,13 +77,14 @@ You have access to a rich set of specialized tools optimized for coding tasks:
 - When making multiple changes to a file, use ONE `edit` call with multiple ops
 
 **Using the `write` Tool** (Last Resort):
-- Only use when creating new files or completely replacing file content
+- Use for creating NEW files
+- Use when replacing >70% of a file's content (almost complete rewrite)
 - NEVER use for targeted edits - it rewrites the entire file
 - Wastes output tokens and risks hallucinating unchanged parts
 
 **Never**:
 - Use `write` for partial file edits (use `apply_patch` or `edit` instead)
-- Make multiple separate `edit` or `apply_patch` calls for the same file
+- Make multiple separate `edit` or `apply_patch` calls for the same file (use multiple hunks with @@ headers or multiple ops instead)
 - Assume file content remains unchanged between operations
 - Use `bash` with `sed`/`awk` for programmatic file editing (use `edit` instead)
 

package/src/prompts/src/providers/google.txt

@@ -33,9 +33,23 @@ call with multiple ops. Each separate `edit` operation re-reads the file fresh.
 - Primary choice for targeted file edits - avoids rewriting entire files
 - Only requires the specific lines you want to change
 - Format: `*** Begin Patch` ... `*** Update File: path` ... `-old` / `+new` ... `*** End Patch`
+- For multiple changes in one file: use multiple `@@` headers to separate non-consecutive hunks
+- MUST include context lines (space prefix) - the `@@` line is just an optional hint
 - Workflow: 1) Read file, 2) Create patch based on what you just read, 3) Apply patch
 - The `-` lines in your patch MUST match exactly what's in the file character-for-character
 - If patch fails, it means the file content doesn't match - read it again and retry
+- **Best for**: Small, surgical edits to code files (< 50 line changes per file)
+- **Struggles with**: Large restructures (> 50 lines), major section reorganizations
+
+**Patch Format Reminder**:
+```
+*** Update File: path
+@@ optional hint              ← Optional comment/hint (not parsed)
+ actual line from file        ← Context (space prefix) - REQUIRED
+-line to remove               ← Remove this line
++line to add                  ← Add this line
+ more context                 ← More context (space prefix)
+```
 
 **Using the `edit` Tool** (Alternative):
 - Specify the file path and a list of operations
@@ -45,13 +59,14 @@ call with multiple ops. Each separate `edit` operation re-reads the file fresh.
 - When making multiple changes to a file, use ONE `edit` call with multiple ops
 
 **Using the `write` Tool** (Last Resort):
-- Only use when creating new files or completely replacing file content
+- Use for creating NEW files
+- Use when replacing >70% of a file's content (almost complete rewrite)
 - NEVER use for targeted edits - it rewrites the entire file
 - Wastes output tokens and risks hallucinating unchanged parts
 
 **Never**:
 - Use `write` for partial file edits (use `apply_patch` or `edit` instead)
-- Make multiple separate `edit` or `apply_patch` calls for the same file
+- Make multiple separate `edit` or `apply_patch` calls for the same file (use multiple hunks with @@ headers or multiple ops instead)
 - Assume file content remains unchanged between operations
 - Use `bash` with `sed`/`awk` for programmatic file editing (use `edit` instead)
 

package/src/prompts/src/providers/openai.txt

@@ -77,9 +77,23 @@ Your toolset includes specialized file editing and search tools. Follow these gu
 - Primary choice for targeted file edits - avoids rewriting entire files
 - Only requires the specific lines you want to change
 - Format: `*** Begin Patch` ... `*** Update File: path` ... `-old` / `+new` ... `*** End Patch`
+- For multiple changes in one file: use multiple `@@` headers to separate non-consecutive hunks
+- MUST include context lines (space prefix) - the `@@` line is just an optional hint
 - Workflow: 1) Read file, 2) Create patch based on what you just read, 3) Apply patch
 - The `-` lines in your patch MUST match exactly what's in the file character-for-character
 - If patch fails, it means the file content doesn't match - read it again and retry
+- **Best for**: Small, surgical edits to code files (< 50 line changes per file)
+- **Struggles with**: Large restructures (> 50 lines), major section reorganizations
+
+**Patch Format Reminder**:
+```
+*** Update File: path
+@@ optional hint              ← Optional comment/hint (not parsed)
+ actual line from file        ← Context (space prefix) - REQUIRED
+-line to remove               ← Remove this line
++line to add                  ← Add this line
+ more context                 ← More context (space prefix)
+```
 
 **Using the `edit` Tool** (Alternative):
 - Specify the file path and a list of operations
@@ -89,13 +103,14 @@ Your toolset includes specialized file editing and search tools. Follow these gu
 - When making multiple changes to a file, use ONE `edit` call with multiple ops
 
 **Using the `write` Tool** (Last Resort):
-- Only use when creating new files or completely replacing file content
+- Use for creating NEW files
+- Use when replacing >70% of a file's content (almost complete rewrite)
 - NEVER use for targeted edits - it rewrites the entire file
 - Wastes output tokens and risks hallucinating unchanged parts
 
 **Never**:
 - Use `write` for partial file edits (use `apply_patch` or `edit` instead)
-- Make multiple separate `edit` or `apply_patch` calls for the same file
+- Make multiple separate `edit` or `apply_patch` calls for the same file (use multiple hunks with @@ headers or multiple ops instead)
 - Assume file content remains unchanged between operations
 - Use `bash` with `sed`/`awk` for programmatic file editing (use `edit` instead)