@nomad-e/bluma-cli 0.1.54 → 0.1.55

package/dist/main.js

@@ -9930,6 +9930,51 @@ Since you are in an **isolated sandbox**, ALL tools are auto-approved:
 - **Artifact delivery** - Save outputs with \\\`create_artifact\\\`, declare in attachments
 - **Error transparency** - If something fails, explain why and propose alternatives
 
+### \u26A0\uFE0F CRITICAL: message Tool Usage Rules
+
+The \\\`message\\\` tool has TWO types \u2014 use them CORRECTLY:
+
+#### \\\`message_type: "info"\\\` \u2014 INFORMATION ONLY
+- **Purpose**: Report progress, status updates, discoveries, milestones
+- **Use when**: "Step 1/3 complete", "Found the data", "Processing..."
+- **NEVER use for**: Asking questions, requesting decisions, seeking clarification
+- **Does NOT end the turn** \u2014 you continue working
+
+#### \\\`message_type: "result"\\\` \u2014 FINAL DELIVERY
+- **Purpose**: Deliver final output, declare attachments, end your turn
+- **Use when**: Task is complete, artifacts ready for delivery
+- **Use ONCE per turn** \u2014 only at the very end
+- **Ends the turn** \u2014 agent waits for next input
+
+#### \u274C WRONG: Using "info" to ask questions
+\\\`\\\`\\\`typescript
+// DON'T DO THIS:
+message({
+  message_type: "info",
+  content: "Should I generate PDF or Excel?"  // \u2190 WRONG! info is NOT for questions
+})
+\\\`\\\`\\\`
+
+#### \u2705 CORRECT: Use mailbox for questions to Severino
+\\\`\\\`\\\`typescript
+// DO THIS:
+sendMailboxMessage({
+  session_id: "chat_abc123",
+  to_agent: "severino",
+  message_type: "question",
+  content: "Should I generate PDF or Excel?"
+})
+\\\`\\\`\\\`
+
+#### \u2705 CORRECT: Use "info" for actual information
+\\\`\\\`\\\`typescript
+// DO THIS:
+message({
+  message_type: "info",
+  content: "Step 1/3: Data extraction complete. Processing..."
+})
+\\\`\\\`\\\`
+
 ### Work Ethic
 - **No lazy delegation** - Synthesize information before delegating
 - **Verify assumptions** - Check file paths, validate inputs, confirm context
@@ -10271,6 +10316,13 @@ The user **only** sees chat content you send through the \`message\` tool (\`con
 - \`message_type: "result"\` \u2014 **ends the turn**: final answer, deliverable, or a **question** that needs a user reply; then the agent waits for the user.
 - \`message_type: "info"\` \u2014 **non-terminal**: shown in chat, does **not** end the turn. **Expected behavior:** call \`info\` **multiple times** in a single turn whenever there is something worth saying (even briefly). Under-using \`info\` is a **mistake** in this product.
 
+**\u26A0\uFE0F CRITICAL: "info" is for INFORMATION ONLY \u2014 NEVER for asking questions**
+- \`message_type: "info"\` is **ONLY** for reporting progress, discoveries, failures, milestones
+- **NEVER** use \`info\` to ask the user a question or request a decision
+- If you need to ask the user something, use \`ask_user_question\` (local mode) or the mailbox (sandbox mode)
+- \u274C WRONG: \`message({ message_type: "info", content: "Which format do you prefer?" })\`
+- \u2705 CORRECT: \`ask_user_question({ questions: [...] })\` or \`sendMailboxMessage({ message_type: "question", ... })\`
+
 **When to send \`info\`**
 - Before long sequences (many reads, greps, refactors): one short line \u2014 intent and why.
 - Right after **discoveries** (culprit file, likely cause, relevant API, pattern in codebase).
@@ -10280,7 +10332,7 @@ The user **only** sees chat content you send through the \`message\` tool (\`con
 
 Reasoning streams (if any) do **not** replace \`info\` for user-visible narrative \u2014 see \`<reasoning_and_message_info>\`.
 
-If you need an answer from the user, use \`message\` with \`result\`.
+If you need an answer from the user, use \`ask_user_question\` (local) or \`message\` with \`result\` (sandbox).
 When addressing {username}: normalize handles (hyphens/underscores/dots \u2192 spaces, title case, strip trailing digits if any).
 </messages>
 
@@ -11008,9 +11060,18 @@ function decideToolExecution(toolName) {
       reason: "Unknown tool metadata; require confirmation by default."
     };
   }
-  let autoApprove = policy.isSandbox ? metadata.autoApproveInSandbox : metadata.autoApproveInLocal;
+  if (policy.isSandbox) {
+    return {
+      toolName,
+      metadata,
+      autoApprove: true,
+      requiresConfirmation: false,
+      reason: "Production sandbox mode: ALL tools auto-approved for maximum efficiency. Isolated Docker container ensures safety."
+    };
+  }
+  let autoApprove = metadata.autoApproveInLocal;
   const { permissionMode } = getRuntimeConfig();
-  if (permissionMode === "accept_edits" && !policy.isSandbox && (toolName === "edit_tool" || toolName === "file_write")) {
+  if (permissionMode === "accept_edits" && (toolName === "edit_tool" || toolName === "file_write")) {
     autoApprove = true;
   }
   if (planModeForcesConfirmation(toolName)) {
@@ -11021,7 +11082,7 @@ function decideToolExecution(toolName) {
     metadata,
     autoApprove,
     requiresConfirmation: !autoApprove,
-    reason: autoApprove ? policy.isSandbox ? "Tool auto-approved inside workspace sandbox." : "Tool marked safe for local autonomous execution." : "Tool requires confirmation outside sandbox mode."
+    reason: autoApprove ? "Tool marked safe for local autonomous execution." : "Tool requires confirmation outside sandbox mode."
   };
 }
 

package/package.json

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