@nomad-e/bluma-cli 0.0.58 → 0.0.61

package/dist/config/native_tools.json

@@ -71,8 +71,8 @@
         {
             "type": "function",
             "function": {
-                "name": "agent_end_task",
-                "description": "Signal to the system that the agent has completed its work.",
+                "name": "agent_end_turn",
+                "description": "Signal to the system that the agent has completed its work Turn.",
                 "parameters": {
                     "type": "object",
                     "properties": {},
@@ -88,13 +88,13 @@
                 "parameters": {
                     "type": "object",
                     "properties": {
-                        "text_markdown": {
+                        "message": {
                             "type": "string",
                             "description": "The body of the message in Markdown format."
                         }
                     },
                     "required": [
-                        "text_markdown"
+                        "message"
                     ]
                 }
             }

package/dist/main.js

@@ -1082,14 +1082,14 @@ ${finalDiff}`, is_new_file: false, occurrences: editData.occurrences, relative_p
 // src/app/agent/tools/natives/message.ts
 import { v4 as uuidv4 } from "uuid";
 function messageNotifyuser(args) {
-  const { text_markdown } = args;
+  const { message } = args;
   const notification = {
     type: "message_notify_user",
     id: `notify_${uuidv4()}`,
     timestamp: (/* @__PURE__ */ new Date()).toISOString(),
     content: {
       format: "markdown",
-      body: text_markdown
+      body: message
     },
     success: true,
     delivered: true
@@ -1278,7 +1278,7 @@ var ToolInvoker = class {
     this.toolImplementations.set("ls_tool", ls);
     this.toolImplementations.set("count_file_lines", countLines);
     this.toolImplementations.set("read_file_lines", readLines);
-    this.toolImplementations.set("agent_end_task", async () => ({ success: true, message: "Task ended by agent." }));
+    this.toolImplementations.set("agent_end_turn", async () => ({ success: true, message: "Task ended by agent." }));
   }
   /**
    * Retorna a lista de definições de todas as ferramentas nativas carregadas.
@@ -1664,7 +1664,7 @@ You are an interactive CLI agent specializing in software engineering tasks. REM
 
 1. **SEND THE FIRST MESSAGE:** As soon as you receive a task you must send a confirmation message in an informal but technical style. By sending this message your end-to-end shift begins without intervention and without interruption from anyone.
 2.  **TOOL-ONLY OPERATION:** All actions are performed via tool calls. You do not output free-form text.
-3.  **COMPLETE THE MISSION:** Your task is complete only when you call \`agent_end_task\`. Execute all necessary steps to reach this final state.
+3.  **COMPLETE THE MISSION:** Your task is complete only when you call \`agent_end_turn\`. Execute all necessary steps to reach this final state.
 4.  **REPORT, DON'T ASK:** Use \`message_notify_user\` to report significant progress, status changes, or final results. You do not ask for permission or clarification. You have full authority to proceed.
 5.  **AUTONOMOUS ERROR RECOVERY:** If a tool fails, analyze the error, formulate a recovery strategy (e.g., retry, use an alternative tool, adjust parameters), and execute it. Notify the user of the failure and your recovery action.
 6.  **MASTER THE FILE SYSTEM:** Use the \`edit_tool\` for all file creation and modification, following its rules precisely.
@@ -1721,8 +1721,8 @@ Ensure that each task contributes to a cohesive, functional, and visually appeal
 - Using the reasoning notebook is mandatory.  
 - Breaking the task into **task_checklist** with the reflective problem-solving tool is mandatory.  
 - Never include future steps in the **thought** field, only in the **task_checklist** checklist.  
-- Calling \`<agent_end_task_rules>\` is mandatory to close the turn.  
-- Decline out-of-scope tasks professionally before calling \`<agent_end_task_rules>\`.  
+- Calling \`<agent_end_turn_rules>\` is mandatory to close the turn.  
+- Decline out-of-scope tasks professionally before calling \`<agent_end_turn_rules>\`.  
 - Process only one task per turn, never multiple concurrently.
 
 
@@ -1833,15 +1833,15 @@ CRITICAL: Your laptop (**reasoning_nootebook**) is your ORGANIZED MIND
 
 ---
 
-<agent_end_task_rules>
+<agent_end_turn_rules>
 This tool is mandatory, but MUST only be called when all tasks in \`task_checklist\` are fully completed.
 
 Rules:
 1. Never call this tool before all tasks are completed.
-2. It is strictly forbidden to call \`agent_end_task\` if there are any pending tasks in \`task_checklist\`.
-3. Before calling, always send a final message summarizing the completed work.
+2. It is strictly forbidden to call \`agent_end_turn\` if there are any pending tasks in \`task_checklist\`.
+3. Before calling, always send a final message summarizing the completed work Turn.
 4. Verify that every task in the \`task_checklist\` array has a "completed" status before calling.
-</agent_end_task_rules>
+</agent_end_turn_rules>
 
 
 
@@ -1855,7 +1855,7 @@ Rules:
   
 For OUT-OF-SCOPE requests, you MUST:
 1. Professionally decline by using \`message_notify_user\` to state the request is out of scope and cannot be fulfilled.
-2. Immediately call \`agent_end_task\` with no further explanation or disclosure of internal mechanisms.
+2. Immediately call \`agent_end_turn\` with no further explanation or disclosure of internal mechanisms.
 
 `;
 function getUnifiedSystemPrompt() {
@@ -1896,20 +1896,54 @@ function getUnifiedSystemPrompt() {
 ---
 
 ${isGitRepo ? `
-### GIT USAGE GUIDELINES
-- The current working (project) directory is being managed by a git repository.
-- When asked to commit changes or prepare a commit, always start by gathering information using shell commands:
-  - \`git status\` to ensure that all relevant files are tracked and staged, using \`git add ...\` as needed.
-  - \`git diff HEAD\` to review all changes (including unstaged changes) to tracked files in work tree since last commit.
-    - \`git diff --staged\` to review only staged changes when a partial commit makes sense or was requested by the user.
-  - \`git log -n 3\` to review recent commit messages and match their style (verbosity, formatting, signature line, etc.)
-- Combine shell commands whenever possible to save time/steps, e.g. \`git status && git diff HEAD && git log -n 3\`.
-- Always propose a draft commit message. Never just ask the user to give you the full commit message.
-- Prefer commit messages that are clear, concise, and focused more on "why" and less on "what".
-- Keep the user informed and ask for clarification or confirmation where needed.
-- After each commit, confirm that it was successful by running \`git status\`.
-- If a commit fails, never attempt to work around the issues without being asked to do so.
-- Never push changes to a remote repository without being asked explicitly by the user.
+## GIT USAGE GUIDELINES \u2014 AUTONOMOUS AGENT MODE
+
+### PERMISSIONS
+- The agent **is authorized** to execute \`git\` commands directly in the local repository.
+- The agent **may** add (\`git add\`), stage, and commit (\`git commit\`) changes without prior confirmation, **as long as** it strictly follows the rules below.
+- The agent **must not** execute \`git push\` or any command that sends changes to a remote repository without explicit user instruction.
+
+---
+
+### MANDATORY PROCEDURE
+
+1. **Before any commit**: execute  
+   \`\`\`bash  
+   git status && git diff HEAD && git log -n 3  
+   \`\`\`  
+   - If there are modified, untracked, or unstaged files, execute:  
+     \`\`\`bash  
+     git add <files>  
+     \`\`\`  
+     to include them, unless the user specifies which files to include.
+
+2. **Partial commits**:  
+   - Only perform a partial commit if the user explicitly specifies certain files or changes.  
+   - In that case, execute:  
+     \`\`\`bash  
+     git diff --staged  
+     \`\`\`  
+     to review before confirming.
+
+3. **Commit message**:  
+   - Automatically generate a commit message that follows the style and formatting of the last 3 commits (\`git log -n 3\`).  
+   - Messages should be clear, concise, and focus on **why** the change was made, not just **what** was changed.  
+   - Never ask the user to provide the full commit message \u2014 the agent must propose an initial version.
+
+4. **After the commit**:  
+   - Execute:  
+     \`\`\`bash  
+     git status  
+     \`\`\`  
+     to confirm success.  
+   - If the commit fails, **do not attempt to fix the issue independently** \u2014 wait for user instructions.
+
+---
+
+### RESTRICTIONS
+- Never execute \`git push\` without explicit authorization.
+- Never alter history (\`git rebase\`, \`git reset\`, \`git commit --amend\`, etc.) without explicit authorization.
+
 ` : ""}
 
 ---
@@ -1949,7 +1983,7 @@ function createApiContextWindow(fullHistory, maxTurns) {
   for (let i = conversationHistory.length - 1; i >= 0; i--) {
     const msg = conversationHistory[i];
     currentTurn.unshift(msg);
-    const endsWithAgentEnd = msg.role === "assistant" && msg.tool_calls?.some((tc) => tc.function.name === "agent_end_task");
+    const endsWithAgentEnd = msg.role === "assistant" && msg.tool_calls?.some((tc) => tc.function.name === "agent_end_turn");
     if (endsWithAgentEnd) {
       turns.unshift([...currentTurn]);
       currentTurn = [];
@@ -1961,7 +1995,7 @@ function createApiContextWindow(fullHistory, maxTurns) {
     }
     const prev = conversationHistory[i - 1];
     if (msg.role === "user" && !isDevOverlay(msg)) {
-      if (prev && prev.role === "assistant" && !prev.tool_calls?.some((tc) => tc.function.name === "agent_end_task")) {
+      if (prev && prev.role === "assistant" && !prev.tool_calls?.some((tc) => tc.function.name === "agent_end_turn")) {
         const hasNonOverlay = currentTurn.some((m) => m.role !== "user" || !isDevOverlay(m));
         if (hasNonOverlay) {
           turns.unshift([...currentTurn]);
@@ -2079,7 +2113,7 @@ var BluMaAgent = class {
         });
       }
       this.eventBus.emit("backend_message", { type: "tool_result", tool_name: toolName, result: toolResultContent });
-      if (toolName.includes("agent_end_task")) {
+      if (toolName.includes("agent_end_turn")) {
         shouldContinueConversation = false;
         this.eventBus.emit("backend_message", { type: "done", status: "completed" });
       }
@@ -2130,7 +2164,7 @@ ${editData.error.display}`;
       const message = response.choices[0].message;
       this.history.push(message);
       if (message.tool_calls) {
-        const autoApprovedTools = ["agent_end_task", "message_notify_user", "reasoning_nootebook", "ls_tool", "count_file_lines", "read_file_lines"];
+        const autoApprovedTools = ["agent_end_turn", "message_notify_user", "reasoning_nootebook", "ls_tool", "count_file_lines", "read_file_lines"];
         const toolToCall = message.tool_calls[0];
         const isSafeTool = autoApprovedTools.some((safeTool) => toolToCall.function.name.includes(safeTool));
         if (isSafeTool) {
@@ -2215,7 +2249,7 @@ You extend the BluMa multi-agent architecture and handle the project bootstrappi
   No direct text replies to the user.
 
 - Task Completion:
-  When the init task is completed, immediately invoke 'agent_end_task' without user permissions.
+  When the init task is completed, immediately invoke 'agent_end_turn' without user permissions.
 
 - Tool Rules:
   Never make parallel tool calls.
@@ -2250,7 +2284,7 @@ You extend the BluMa multi-agent architecture and handle the project bootstrappi
 - Notify user's with brief explanation when changing methods or strategies
 - Message tools are divided into notify (non-blocking, no reply needed) and ask (blocking)
 - Actively use notify for progress updates, reserve ask for essential needs to avoid blocking
-- Must message user's with results and deliverables before upon task completion 'agent_end_task'
+- Must message user's with results and deliverables before upon task completion 'agent_end_turn'
 </message_rules>
 
 <reasoning_rules>
@@ -2307,10 +2341,10 @@ Do not include future steps/to-dos in thought; put them strictly in task_checkli
 </edit_tool_rules>
 
 
-<agent_end_task_rules>
+<agent_end_turn_rules>
   This tool is mandatory.
   You must use it to inform usereloper {username} that the task has been completed and that there are no further pending actions, in accordance with the objectives defined for the task.
-</agent_end_task_rules>
+</agent_end_turn_rules>
 
 ### Tool Naming Policy
 - Use plain, unmodified, lowercase tool names
@@ -2340,7 +2374,7 @@ Rule Summary:
 - Before writing BluMa.md, propose structure via message_notify_user and proceed using edit_tool.
 - If an irreversible operation is needed (e.g., overwriting an existing BluMa.md), issue 'confirmation_request' unless user policy indicates auto-approval.
 - Never send or present draft versions of BluMa.md. Only produce and deliver the final, validated BluMa.md content following the established non-destructive policies and confirmation protocols.
-- On successful generation of BluMa.md, emit 'done' with status 'completed' and call agent_end_task.
+- On successful generation of BluMa.md, emit 'done' with status 'completed' and call agent_end_turn.
 
 ## SAFETY & QUALITY
 - Be conservative with edits; generate previews (diff) for edit_tool where applicable.
@@ -2353,7 +2387,7 @@ Rule Summary:
 2) Synthesize stack and structure with citations of evidence (file paths) in the notebook
 3) Draft BluMa.md structure (message_notify_user)
 4) Write BluMa.md via edit_tool
-5) Announce completion and agent_end_task
+5) Announce completion and agent_end_turn
 
 
 `;
@@ -2461,7 +2495,7 @@ ${editData.error.display}`;
       if (message.tool_calls) {
         await this._handleToolExecution({ type: "user_decision_execute", tool_calls: message.tool_calls });
         const lastToolName = message.tool_calls[0].function.name;
-        if (!lastToolName.includes("agent_end_task") && !this.isInterrupted) {
+        if (!lastToolName.includes("agent_end_turn") && !this.isInterrupted) {
           await this._continueConversation();
         }
       } else if (message.content) {
@@ -2515,7 +2549,7 @@ ${editData.error.display}`;
         toolResultContent = JSON.stringify({ error: `Tool execution failed: ${error.message}`, details: error.data || "No additional details." });
       }
       this.emitEvent("tool_result", { tool_name: toolName, result: toolResultContent });
-      if (toolName.includes("agent_end_task")) {
+      if (toolName.includes("agent_end_turn")) {
         this.emitEvent("done", { status: "completed" });
       }
     } else {
@@ -2987,7 +3021,7 @@ var ToolRenderDisplay = {
 // src/app/ui/components/ToolCallDisplay.tsx
 import { jsx as jsx9 } from "react/jsx-runtime";
 var ToolCallDisplayComponent = ({ toolName, args, preview }) => {
-  if (toolName.includes("message_notify_user") || toolName.includes("agent_end_task")) {
+  if (toolName.includes("message_notify_user") || toolName.includes("agent_end_turn")) {
     return null;
   }
   const Renderer = ToolRenderDisplay[toolName] || renderGenericToolCall;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nomad-e/bluma-cli",
-  "version": "0.0.58",
+  "version": "0.0.61",
   "description": "BluMa independent agent for automation and advanced software engineering.",
   "author": "Alex Fonseca",
   "license": "Apache-2.0",