@nomad-e/bluma-cli 0.1.41 → 0.1.42

package/dist/config/native_tools.json

@@ -40,32 +40,73 @@
       "type": "function",
       "function": {
         "name": "edit_tool",
-        "description": "Replaces exact text in a file or creates a new file. Prefer **one** well-scoped edit over many tiny edits.\n\n**Critical — avoid line-by-line surgery:**\n- Do **not** change the same file in a dozen sequential calls with one line each; that drifts, breaks whitespace, and often fails.\n- After `read_file_lines`, copy a **single contiguous block** (whole function, whole component, or 5–20 lines with unique context) into `old_string`, then replace with your revised block in `new_string`.\n- If the tool reports no match or ambiguous match, **widen** `old_string` (more surrounding lines) or fix indentation to match the file **exactly** — do not blindly retry a one-line fragment.\n\n**CLI note:** The user may press Ctrl+O to see more lines of a **truncated** read/shell preview in the terminal. That view is UI-only and may still omit lines; always trust `read_file_lines` for exact text and whitespace before calling `edit_tool`.\n\n**Checklist:**\n1. Read the file first; use literal newlines in `old_string`/`new_string` (not the two-character sequence backslash-n).\n2. `expected_replacements` must match how many times `old_string` appears (default 1).\n3. New file: `old_string` empty, `new_string` full content.",
+        "description": "Replaces exact text in file(s) or creates files. **Prefer batching:** use `edits` with multiple `{file_path, old_string, new_string}` entries in **one** call when you need several replacements (same or different files) to save model turns. Order matters: later entries see the result of earlier ones on the same path.\n\n**Single-file mode:** `file_path` + `old_string` + `new_string` (legacy).\n\n**Avoid line-by-line surgery:** do not chain dozens of one-line calls; batch related changes or use one wide `old_string` block.\n- After `read_file_lines`, copy a **contiguous block** with unique context into `old_string`.\n- If no match, widen `old_string` or fix indentation to match the file **exactly**.\n\n**CLI:** Ctrl+O expands truncated read/shell previews only; trust `read_file_lines` for exact bytes.\n\n**Checklist:** literal newlines in strings (not `\\\\n`). `expected_replacements` per entry. New file: `old_string` empty.",
         "parameters": {
           "type": "object",
           "properties": {
             "file_path": {
               "type": "string",
-              "description": "The absolute or relative path to the file. The tool will correctly resolve the path for the current operating system."
+              "description": "Path to the file (single-edit mode only). Omit when using `edits[]`."
             },
             "old_string": {
               "type": "string",
-              "description": "The exact text to be replaced. To ensure accuracy, this should be a unique, multi-line segment from the file, including all original indentation and whitespace. Do not manually escape newlines (use literal newlines, not '\\n'). For creating a new file, this must be an empty string."
+              "description": "Exact text to replace (single-edit mode). Empty string only to create a new file. Omit when using `edits[]`."
             },
             "new_string": {
               "type": "string",
-              "description": "The new text that will replace `old_string`. Match the indentation and formatting of the surrounding code to maintain code quality. Do not manually escape newlines."
+              "description": "Replacement text (single-edit mode). Omit when using `edits[]`."
             },
             "expected_replacements": {
               "type": "integer",
-              "description": "Optional. The number of occurrences to replace. Defaults to 1. If you expect to replace multiple instances of `old_string`, set this value accordingly.",
+              "description": "Single-edit mode: occurrences to replace (default 1).",
               "default": 1
+            },
+            "edits": {
+              "type": "array",
+              "maxItems": 64,
+              "description": "Batch mode: several edits in one tool invocation. Each item is one replacement. Same file: list edits in application order.",
+              "items": {
+                "type": "object",
+                "properties": {
+                  "file_path": {
+                    "type": "string",
+                    "description": "Target file for this replacement."
+                  },
+                  "old_string": {
+                    "type": "string",
+                    "description": "Exact snippet to replace; empty only when creating that path as a new file."
+                  },
+                  "new_string": {
+                    "type": "string",
+                    "description": "New content for that replacement."
+                  },
+                  "expected_replacements": {
+                    "type": "integer",
+                    "description": "Occurrences to replace for this entry (default 1).",
+                    "default": 1
+                  }
+                },
+                "required": [
+                  "file_path",
+                  "old_string",
+                  "new_string"
+                ]
+              }
             }
           },
-          "required": [
-            "file_path",
-            "old_string",
-            "new_string"
+          "anyOf": [
+            {
+              "required": [
+                "file_path",
+                "old_string",
+                "new_string"
+              ]
+            },
+            {
+              "required": [
+                "edits"
+              ]
+            }
           ]
         }
       }
@@ -190,13 +231,13 @@
       "type": "function",
       "function": {
         "name": "message",
-        "description": "Send messages to user. CRITICAL: After sending a message, you MUST use result to end your turn and wait for user response. Use info ONLY for mid-task updates when you will continue working immediately after.",
+        "description": "Primary user-visible channel — use it generously. Call message_type \"info\" frequently during a turn (progress, findings, errors, next steps); multiple info calls per turn are required for good UX. The turn does not stop on \"info\". Use message_type \"result\" once when you finish this turn (final answer, deliverable, or question for the user); then the agent waits.",
         "parameters": {
           "type": "object",
           "properties": {
             "content": {
               "type": "string",
-              "description": "Message content in Markdown format."
+              "description": "Markdown body shown in the chat (user's language when appropriate)."
             },
             "message_type": {
               "type": "string",
@@ -204,7 +245,7 @@
                 "info",
                 "result"
               ],
-              "description": "info = mid-task update (you continue working). result = end turn and wait for user (use this after questions, completions, or when you need user input)."
+              "description": "Prefer \"info\" often while working (does not end turn). Use \"result\" only once to end the turn."
             },
             "attachments": {
               "type": "array",