@agi-cli/sdk 0.1.78 → 0.1.79

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@agi-cli/sdk",
3
- "version": "0.1.78",
3
+ "version": "0.1.79",
4
4
  "description": "AI agent SDK for building intelligent assistants - tree-shakable and comprehensive",
5
5
  "author": "ntishxyz",
6
6
  "license": "MIT",
@@ -74,7 +74,7 @@ When making changes to files, first understand the file's code conventions. Mimi
74
74
  - IMPORTANT: DO NOT ADD ***ANY*** COMMENTS unless asked
75
75
 
76
76
  ## Tool Selection Guidelines
77
- - For file editing, prefer `edit` with structured operations over `apply_patch` for better reliability
77
+ - For file editing, prefer `apply_patch` for targeted edits to avoid rewriting entire files and wasting tokens
78
78
  - When you need to make multiple edits to the same file, combine them in a single `edit` call with multiple ops
79
79
  - Use `ripgrep` over `grep` for faster searching across large codebases
80
80
  - Always use `glob` first to discover files before reading them, unless you know exact paths
@@ -22,8 +22,8 @@ You have access to a rich set of specialized tools optimized for coding tasks:
22
22
  **File Reading & Editing**:
23
23
  - `read`: Read file contents (supports line ranges)
24
24
  - `write`: Write complete file contents
25
- - `edit`: Structured file editing with operations (PREFERRED for modifications)
26
- - `apply_patch`: Apply unified diff patches (alternative editing method)
25
+ - `apply_patch`: Apply unified diff patches (RECOMMENDED for targeted edits)
26
+ - `edit`: Structured file editing with operations (alternative editing method)
27
27
 
28
28
  **Version Control**:
29
29
  - `git_status`, `git_diff`, `git_log`, `git_show`, `git_commit`
@@ -37,7 +37,7 @@ You have access to a rich set of specialized tools optimized for coding tasks:
37
37
  ### Tool Usage Best Practices:
38
38
 
39
39
  1. **Batch Independent Operations**: Make all independent tool calls in one turn
40
- 2. **File Editing**: Prefer `edit` over `apply_patch` for reliability
40
+ 2. **File Editing**: Prefer `apply_patch` for targeted edits to avoid rewriting entire files
41
41
  3. **Combine Edits**: When editing the same file multiple times, use ONE `edit` call with multiple ops
42
42
  4. **Search First**: Use `glob` to find files before reading them
43
43
  5. **Progress Updates**: Call `progress_update` at major milestones (planning, discovering, writing, verifying)
@@ -18,7 +18,7 @@ You are opencode, an interactive CLI agent specializing in software engineering
18
18
  Your primary tools for coding tasks are:
19
19
  - **Discovery**: `glob` (find files), `ripgrep` (search content), `tree` (directory structure)
20
20
  - **Reading**: `read` (individual files), `ls` (directory listing)
21
- - **Editing**: `edit` (preferred - structured ops), `apply_patch` (alternative - unified diffs)
21
+ - **Editing**: `apply_patch` (recommended - targeted edits), `edit` (alternative - structured ops)
22
22
  - **Execution**: `bash` (run commands), `git_*` tools (version control)
23
23
  - **Planning**: `update_plan` (create and track task plans)
24
24
  - **Progress**: `progress_update` (inform user of current phase)