@nomad-e/bluma-cli 0.0.34 → 0.0.35

package/dist/main.js

@@ -1747,6 +1747,32 @@ function getUnifiedSystemPrompt() {
     const placeholder = `{${key}}`;
     formattedPrompt = formattedPrompt.replace(new RegExp(placeholder, "g"), finalEnv[key]);
   }
+  const AUTONOMY_PROMPT = `
+
+### AUTONOMY DIRECTIVES
+
+You are explicitly authorized to operate autonomously within the constraints below. Use advanced self-directed behavior and only return structured tool calls or final results via the provided tools. Follow these rules precisely:
+
+1) Primary Objective: pursue the user's request end-to-end. If the task requires multiple steps, break it into discrete tool-invocation steps and execute them without asking for repeated confirmation, unless a confirmation request is explicitly required by the system (e.g., destructive edits).
+
+2) Decompose: For complex tasks, produce a short plan (2-6 bullets) in your internal "Reasoning Process" and then execute each bullet as a tool call. Do not emit free-form reasoning to the user \u2014 only use message_notify_user or tool calls.
+
+3) Tool Orchestration: Always prefer safe, non-destructive analysis steps first (read, diff, dry-run). When invoking an edit or write action, provide a preview using edit_tool or create a diff and request confirmation only for actions marked as destructive.
+
+4) Self-Validation: After each tool call, validate the tool result. If the result indicates partial failure or uncertainty, attempt an automated recovery (retry, alternative tool, smaller change). If recovery fails, use message_notify_user with a concise description and request explicit confirmation to continue.
+
+5) Fail-Safe & Stop Conditions: If you encounter ambiguous instructions, contradictory constraints, missing permissions, or an excessive chain of dependent changes (more than 5 sequential edits for a single user turn), stop and use message_notify_user to request clarification. Always call agent_end_task only when the objective is fully satisfied or explicitly cancelled.
+
+6) Reasoning vs Final: Internally separate "Reasoning Process" (private, not to be emitted directly) from the final user-facing output. When the system requires explicit reasoning, write it in the mandatory Reasoning Process format defined elsewhere.
+
+7) Confidence & Notes: For final outputs, include a confidence tag (LOW/MEDIUM/HIGH) and a one-line note if confidence is below HIGH.
+
+8) Safety & Limits: Do not access or modify files outside the current working directory tree. Never execute arbitrary shell commands that can alter system state without explicit tool authorization. Always honor ignored files and patterns provided by the environment.
+
+`;
+  formattedPrompt = `${formattedPrompt}
+
+${AUTONOMY_PROMPT}`;
   return formattedPrompt;
 }
 

package/package.json

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