@nomad-e/bluma-cli 0.1.62 → 0.1.63

package/dist/main.js

@@ -319,35 +319,13 @@ var init_sandbox_policy = __esm({
     init_runtime_config();
     init_permission_rules();
     BLOCKED_COMMAND_PATTERNS = [
-      { pattern: /^sudo\s+/i, reason: "Privilege escalation is not allowed." },
-      { pattern: /^doas\s+/i, reason: "Privilege escalation is not allowed." },
-      { pattern: /^su\s+/i, reason: "Privilege escalation is not allowed." },
-      { pattern: /^pkexec\s+/i, reason: "Privilege escalation is not allowed." },
-      { pattern: /\bmkfs\./i, reason: "Disk formatting commands are blocked." },
-      { pattern: /\bdd\s+.*of=\/dev\/(sd|hd|nvme)/i, reason: "Raw disk writes are blocked." },
-      { pattern: /\brm\s+(-[rf]+\s+)*\/($|\s)/i, reason: "Deleting filesystem roots is blocked." },
-      { pattern: /\brm\s+-[rf]*\s+~($|\s)/i, reason: "Deleting home roots is blocked." },
-      { pattern: /\bcurl\s+.*\|\s*(ba)?sh/i, reason: "Pipe-to-shell remote execution is blocked." },
-      { pattern: /\bwget\s+.*\|\s*(ba)?sh/i, reason: "Pipe-to-shell remote execution is blocked." }
+      // No command patterns blocked — sandbox isolation handles safety
     ];
     HIGH_RISK_COMMAND_PATTERNS = [
-      /\brm\s+-[rf]/i,
-      /\bmv\s+.+\s+\/(?!tmp\b)/i,
-      /\bchmod\b/i,
-      /\bchown\b/i,
-      /\bssh\b/i,
-      /\bscp\b/i,
-      /\brsync\b/i,
-      /\bdocker\b/i,
-      /\bkubectl\b/i
+      // No high-risk patterns — all commands allowed inside sandbox
     ];
     MODERATE_RISK_COMMAND_PATTERNS = [
-      /\bnpm\s+(install|update|uninstall)\b/i,
-      /\bpnpm\s+(add|install|update|remove)\b/i,
-      /\byarn\s+(add|install|remove)\b/i,
-      /\buv\s+(add|remove|sync)\b/i,
-      /\bpip\s+install\b/i,
-      /\bgit\s+(commit|push|rebase|reset|clean)\b/i
+      // No moderate-risk patterns — all commands allowed inside sandbox
     ];
   }
 });
@@ -14221,37 +14199,28 @@ You are a worker agent spawned by the BluMa Coordinator to execute specific soft
   You are a BluMa Worker Agent. You execute tasks delegated by the Coordinator.
   Maintain professionalism and technical excellence.
 
-- **Communication:**
-  - ALL messages must be sent via the \`message\` tool
-  - No direct text replies to the user
-  - Report progress frequently using \`message\` with \`message_type: "info"\`
-  - Report final results using \`message\` with \`message_type: "result"\`
-
-- **Task Completion:**
-  - When your task is completed, immediately invoke \`agent_end_turn\` without user permissions
-  - Before ending, ensure all work is committed and tested
-  - Report the final state (e.g., commit hash, test results, file paths)
-
 - **Tool Rules:**
   - Never make parallel tool calls
   - Only use the defined tools with their exact names
   - Read before editing (\`read_file_lines\`, \`grep_search\`, \`ls_tool\`)
   - Verify changes with tests or typechecks when applicable
+  - Note: "Never make parallel tool calls" applies to tool invocations only \u2014 spawning sub-workers is allowed and encouraged for parallelizable work
 
 - **Autonomy:**
   - Act 100% autonomously within your task scope
   - Do not ask for clarification unless the task is fundamentally blocked
   - Use the notebook for internal reasoning and planning
   - If you encounter errors, attempt to resolve them before reporting failure
-  - Note: "Never make parallel tool calls" applies to tool invocations only \u2014 spawning sub-workers is allowed and encouraged for parallelizable work
 
 - **Sub-Delegation (Advanced):**
   - You CAN spawn sub-workers using \`spawn_agent()\` for parallelizable subtasks
+  - **Limit sub-delegation depth to 2 levels** to avoid runaway agent trees and token exhaustion
   - Only sub-delegate when: (a) task has independent parts, (b) you need fresh context, or (c) verification should be independent
   - Do NOT sub-delegate simple tasks that you can complete directly
   - Always provide self-contained prompts to sub-workers
   - Use \`wait_agent()\` to wait for sub-worker completion
   - Synthesize sub-worker results before reporting to Coordinator
+  - Sub-workers inherit the same sandbox policy \u2014 do not attempt to escalate privileges or bypass sandbox restrictions
 
 - **Mailbox Communication:**
   - You can send messages to the Coordinator via mailbox for:
@@ -14277,6 +14246,23 @@ You are a worker agent spawned by the BluMa Coordinator to execute specific soft
 ---
 
 ### CRITICAL COMMUNICATION PROTOCOL
+
+**Message Tool Usage:**
+- ALL messages must be sent via the \`message\` tool \u2014 no direct text replies
+- Report progress frequently using \`message\` with \`message_type: "info"\` (non-blocking)
+- Report final results using \`message\` with \`message_type: "result"\` (ends turn)
+- Use \`ask_user_question\` only when fundamentally blocked (blocking)
+- Reply immediately to new user messages before other operations
+- First reply must be brief, confirming receipt of the task
+- Notify user with brief explanation when changing methods or strategies
+- Must message user with results and deliverables before calling \`agent_end_turn\`
+
+**Task Completion:**
+- When your task is completed, immediately invoke \`agent_end_turn\` without user permissions
+- Before ending, ensure all work is committed and tested
+- Report the final state (e.g., commit hash, test results, file paths)
+
+**Protocol Rules:**
 - Only tool_calls are allowed for assistant replies. Never include a "content" field.
 - Always use tools to respond, retrieve data, compute or transform. Await a valid tool response before any final message.
 - Zero tolerance for protocol violations.
@@ -14292,16 +14278,6 @@ You are a worker agent spawned by the BluMa Coordinator to execute specific soft
 - Locale: {locale}
 </current_system_environment>
 
-<message_rules>
-- Communicate with the user via \`message\` tool instead of direct text responses
-- Reply immediately to new user messages before other operations
-- First reply must be brief, only confirming receipt of the task
-- Notify user 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 with results and deliverables before calling \`agent_end_turn\`
-</message_rules>
-
 <reasoning_rules>
 # YOUR THINKING ON A NOTEBOOK - MANDATORY USE
 CRITICAL: Your notebook (reasoning_notebook) is your ORGANIZED MIND
@@ -14342,7 +14318,7 @@ Do not include future steps/to-dos in thought; put them strictly in to_do, using
   - "[\u2713]" \u2192 for tasks already completed
 </reasoning_rules>
 
-<edit_tool_rules>  
+<edit_tool_rules>
 - Use this tool to perform precise text replacements inside files based on exact literal matches.
 - Can be used to create new files or directories implicitly by targeting non-existing paths.
 - Suitable for inserting full content into a file even if the file does not yet exist.
@@ -14350,10 +14326,6 @@ Do not include future steps/to-dos in thought; put them strictly in to_do, using
 - Always prefer this tool over shell_command when performing structured edits or creating files with specific content.
 - Ensure **old_string** includes 3+ lines of exact context before and after the target if replacing existing content.
 - For creating a new file, provide an **old_string** that matches an empty string or placeholder and a complete **new_string** with the intended content.
-- When generating or modifying todo.md files, prefer this tool to insert checklist structure and update status markers.
-- After completing any task in the checklist, immediately update the corresponding section in todo.md using this tool.
-- Reconstruct the entire file from task planning context if todo.md becomes outdated or inconsistent.
-- Track all progress related to planning and execution inside todo.md using text replacement only.
 </edit_tool_rules>
 
 <agent_end_turn>

package/package.json

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