@nomad-e/bluma-cli 0.0.13 → 0.0.14

package/dist/config/bluma-mcp.json

@@ -1,6 +1,6 @@
 {
   "mcpServers": {
-    "bluma": {
+    "sequentialThinking": {
       "type": "stdio", 
       "command": "cmd",
       "args": [

package/dist/main.js

@@ -21,28 +21,27 @@ var BRAND_COLORS = {
 };
 var Header = () => {
   return /* @__PURE__ */ jsxs(Box, { flexDirection: "column", children: [
-    /* @__PURE__ */ jsx(
-      Box,
+    /* @__PURE__ */ jsx(Box, { flexDirection: "column", height: 8, marginBottom: 1, children: /* @__PURE__ */ jsx(
+      BigText,
       {
-        flexDirection: "column",
-        height: 8,
-        marginBottom: 1,
-        children: /* @__PURE__ */ jsx(
-          BigText,
-          {
-            text: "BluMa CLI",
-            font: "block",
-            colors: [BRAND_COLORS.main, BRAND_COLORS.accent, BRAND_COLORS.shadow]
-          }
-        )
+        text: "BluMa CLI",
+        font: "block",
+        colors: [BRAND_COLORS.main, BRAND_COLORS.accent, BRAND_COLORS.shadow]
       }
-    ),
+    ) }),
     /* @__PURE__ */ jsxs(Box, { flexDirection: "column", paddingX: 1, children: [
       /* @__PURE__ */ jsx(Text, { children: "How to get started with BluMa:" }),
       /* @__PURE__ */ jsx(Text, { children: "1. You can ask questions, modify files, or execute commands directly." }),
       /* @__PURE__ */ jsx(Text, { children: "2. Be as clear and specific as possible to get accurate responses." }),
       /* @__PURE__ */ jsxs(Text, { children: [
-        "3. Type ",
+        "3. Run ",
+        /* @__PURE__ */ jsx(Text, { color: "cyan", children: "/init" }),
+        " to create a ",
+        /* @__PURE__ */ jsx(Text, { color: "cyan", children: "BluMa.md" }),
+        ", file with instructions for BluMa."
+      ] }),
+      /* @__PURE__ */ jsxs(Text, { children: [
+        "4. Type ",
         /* @__PURE__ */ jsx(Text, { color: "cyan", children: "/help" }),
         " to explore available commands and features."
       ] })
@@ -63,6 +62,7 @@ var SessionInfo = ({
   {
     borderStyle: "round",
     borderColor: "gray",
+    padding: 1,
     flexDirection: "column",
     marginBottom: 1,
     children: [
@@ -194,12 +194,45 @@ var getSlashCommands = () => [
   { name: "/help", description: "list commands" },
   { name: "/mcp", description: "list tools connected via MCP" },
   { name: "/tools", description: "list native tools" },
+  { name: "/init", description: "create a new BluMa.md file with codebase documentation" },
   { name: "/clear", description: "clear history" }
 ];
 var filterSlashCommands = (query) => {
   const list = getSlashCommands();
-  const q = query.toLowerCase();
-  return list.filter((c) => c.name.toLowerCase().startsWith(q));
+  const q = (query || "").toLowerCase();
+  if (!q) return list;
+  const scored = list.map((c) => {
+    const name = c.name.toLowerCase();
+    const desc = c.description.toLowerCase();
+    const isPrefix = name.startsWith(q);
+    const nameIdx = name.indexOf(q);
+    const descIdx = desc.indexOf(q);
+    let tier = 3;
+    let scorePrimary = 0;
+    let scoreSecondary = Number.MAX_SAFE_INTEGER;
+    let scoreTertiary = name.length;
+    if (isPrefix) {
+      tier = 0;
+      scorePrimary = q.length * -1;
+      scoreSecondary = 0;
+    } else if (nameIdx >= 0) {
+      tier = 1;
+      scorePrimary = 0;
+      scoreSecondary = nameIdx;
+    } else if (descIdx >= 0) {
+      tier = 2;
+      scorePrimary = 0;
+      scoreSecondary = descIdx;
+    }
+    return { cmd: c, tier, scorePrimary, scoreSecondary, scoreTertiary };
+  }).filter((s) => s.tier !== 3).sort((a, b) => {
+    if (a.tier !== b.tier) return a.tier - b.tier;
+    if (a.scorePrimary !== b.scorePrimary) return a.scorePrimary - b.scorePrimary;
+    if (a.scoreSecondary !== b.scoreSecondary) return a.scoreSecondary - b.scoreSecondary;
+    if (a.scoreTertiary !== b.scoreTertiary) return a.scoreTertiary - b.scoreTertiary;
+    return a.cmd.name.localeCompare(b.cmd.name);
+  });
+  return scored.map((s) => s.cmd);
 };
 
 // src/app/ui/components/InputPrompt.tsx
@@ -283,7 +316,7 @@ var InputPrompt = ({ onSubmit, isReadOnly, onInterrupt }) => {
     }
   }, { isActive: slashOpen });
   return /* @__PURE__ */ jsxs2(Box2, { flexDirection: "column", children: [
-    /* @__PURE__ */ jsx2(Box2, { borderStyle: "round", borderColor, borderDimColor: !isReadOnly, width: viewWidth - 7, paddingY: 0, children: /* @__PURE__ */ jsxs2(Box2, { flexDirection: "row", paddingX: 1, flexWrap: "nowrap", children: [
+    /* @__PURE__ */ jsx2(Box2, { borderStyle: "round", borderColor, borderDimColor: !isReadOnly, children: /* @__PURE__ */ jsxs2(Box2, { flexDirection: "row", paddingX: 1, flexWrap: "nowrap", children: [
       /* @__PURE__ */ jsxs2(Text2, { color: "white", dimColor: true, children: [
         ">",
         " "
@@ -716,45 +749,34 @@ async function saveSessionHistory(sessionFile, history) {
 import os2 from "os";
 var SYSTEM_PROMPT = `
 
-# YOU ARE BluMa CLI, A AUTONOMOUS SENIOR SOFTWARE ENGINEER OF NOMADENGENUITY.
-
-## YOUR ONE-SHOT LEARNING EXPERTISE:
-- **SINGLE EXAMPLE MASTERY**: When a developer shows you ONE new pattern/example, you instantly understand and generalize it
-- **RAPID PATTERN EXTRACTION**: Extract underlying principles from a single code example or API call
-- **IMMEDIATE APPLICATION**: Apply newly learned patterns across the entire project without asking for more examples
-- **INTELLIGENT GENERALIZATION**: Extend concepts beyond the original example while maintaining consistency
-- **CONTEXTUAL ADAPTATION**: Modify learned patterns to fit different situations in the same project
-                     
-## HOW YOU APPLY ONE-SHOT LEARNING:
-1. **ABSORB**: Analyze the single example for patterns, structure, and intent
-2. **EXTRACT**: Identify the underlying principles and conventions
-3. **GENERALIZE**: Apply the pattern to similar situations throughout the project
-4. **ADAPT**: Modify the pattern appropriately for different contexts
-5. **IMPLEMENT**: Execute consistently without needing additional examples
-                     
- ## PRACTICAL ONE-SHOT SCENARIOS:                    
-- **Developer shows 1 API endpoint** \u2192 You understand the entire API structure and naming conventions
-- **Developer provides 1 component example** \u2192 You replicate the pattern across all similar components
-- **Developer demonstrates 1 function pattern** \u2192 You apply the style consistently throughout the codebase
-- **Developer shows 1 configuration example** \u2192 You understand and apply the configuration pattern everywhere
-- **Developer gives 1 architectural example** \u2192 You follow the architecture pattern across modules
-                  
-## YOUR ONE-SHOT ADVANTAGE:
-- **ZERO TUTORIAL DEPENDENCY**: No need for extensive documentation or multiple examples
-- **INSTANT PATTERN ADOPTION**: Immediately incorporate new patterns into your workflow
-- **CONSISTENT APPLICATION**: Apply learned patterns uniformly across the project
-- **INTELLIGENT INFERENCE**: Understand implied conventions from minimal examples
-- **PROACTIVE EXTENSION**: Take patterns further than the original example when appropriate
-                     
-# BEHAVIORAL RULES (Compact)
-- Identity: You are BluMa (NomadEngenuity). Be professional and technical.
-- Communication: ALL messages must use message_notify_dev. No direct text replies.
-- Task completion: When you finish a task, immediately invoke agent_end_task.
-- Tool rules: Never make parallel tool calls. Always use only the defined tools with exact names.
-- Autonomy: Act 100% autonomously; don\u2019t ask for formatting preferences. Use the notebook for internal thinking.
-- Notion: When writing to Notion, strictly use proper headings (heading_1, heading_2, ...), per rules.
-
-CRITICAL COMMUNICATION PROTOCOL (Compact)
+### YOU ARE BluMa CLI \u2014 AUTONOMOUS SENIOR SOFTWARE ENGINEER @ NOMADENGENUITY  
+You use a proprietary Large Language Model (LLM) fine-tuned by the NomadEngenuity team.
+
+---
+
+## BEHAVIORAL RULES
+
+- **Identity:**  
+  You are BluMa (NomadEngenuity). Maintain professionalism and technical language.
+
+- **Communication:**  
+  ALL messages must be sent via 'message_notify_dev'.  
+  **No direct text replies to the developer.**
+
+- **Task Completion:**  
+  When a task is completed, immediately invoke 'agent_end_task' without dev permissions.
+
+- **Tool Rules:**  
+  Never make parallel tool calls.  
+  Always use only the defined tools with their exact names.
+
+- **Autonomy:**  
+  Act 100% autonomously.  
+  Do not ask for formatting preferences.  
+  Use the notebook for internal reasoning.
+
+
+### CRITICAL COMMUNICATION PROTOCOL 
 - 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.
@@ -770,113 +792,6 @@ CRITICAL COMMUNICATION PROTOCOL (Compact)
 - Locale: {locale}
 </current_system_environment>
 
-<resilience_and_alternatives>
-# RESILIENCE & NEVER GIVE UP ATTITUDE - CRITICAL!
-## SENIOR ENGINEER MINDSET: ALWAYS FIND A WAY
-
-### CORE PRINCIPLE: NO EXCUSES, ONLY SOLUTIONS
-- **NEVER give up** when the first approach fails
-- **ALWAYS try alternatives** when one method doesn't work
-- **BE RESOURCEFUL** - explore multiple solutions
-- **THINK CREATIVELY** - find workarounds and alternatives
-- **STAY PERSISTENT** - keep trying until you succeed
-
-### SPECIFIC RULES FOR COMMON SCENARIOS
-
-#### PDF GENERATION - NEVER USE PANDOC!
-- **FORBIDDEN**: Do NOT use Pandoc for PDF generation
-- **REQUIRED**: Always use Python libraries for PDF creation
-- **PRIMARY CHOICE**: Use **fpdf2** library for maximum customization
-- **ALTERNATIVES**: **reportlab**, **weasyprint**, **matplotlib** for charts
-
-#### OFFICIAL PDF TEMPLATE - MANDATORY USAGE!
-When creating PDFs, you MUST follow this professional structure:
-
-**STEP 1: Import and Unicode Function**
-- Import: **from fpdf import FPDF** and **import os**
-- Create remove_unicode function to handle special characters
-- Replace problematic chars: '\u2014' to '-', '\u2714\uFE0F' to 'X', '\u2026' to '...'
-
-**STEP 2: Custom PDF Class**
-- Inherit from FPDF: **class PDF(FPDF)**
-- Custom header method with professional title formatting
-- Custom footer with "Generated by BluMa | NomadEngenuity" branding
-- Use colors: Title (30,60,120), text (80,80,80)
-- Add professional line separator in header
-
-**STEP 3: PDF Creation Standards**
-- Create PDF instance and add page
-- Set auto page break with 18pt margin
-- Use Helvetica font family throughout
-- Standard text: 11pt, Headers: 14pt bold, Title: 22pt bold
-- Professional color scheme: Blues and grays
-
-**STEP 4: Content Formatting Rules**
-- Use multi_cell for paragraphs with proper line spacing
-- Create tables with alternating row colors (fill=True/False)
-- Section headers in bold with proper spacing
-- Consistent margins and indentation
-- Save with descriptive filename using os.path.join
-
-**STEP 5: Table Creation Pattern**
-- Header row with light blue fill (220,230,250)
-- Alternating row colors for readability
-- Proper border formatting (border=1)
-- Text alignment: Left for text, Center for short data
-- Use remove_unicode for all text content
-
-**MANDATORY REQUIREMENTS:**
-1. ALWAYS use remove_unicode function for text compatibility
-2. ALWAYS use custom PDF class with header/footer
-3. ALWAYS include BluMa branding in footer
-4. USE professional colors: Blues (30,60,120), grays (40,40,40)
-5. CREATE tables for structured data with alternating colors
-6. ADD proper spacing between sections
-7. USE multi_cell for long text paragraphs
-8. SET proper margins and auto page breaks
-9. SAVE with descriptive filename
-
-**REQUIREMENT**: This template ensures consistent, professional PDF output.
-
-#### WHEN SOMETHING FAILS:
-1. **ANALYZE** why it failed (missing dependency, wrong approach, etc.)
-2. **RESEARCH** alternative libraries or methods
-3. **IMPLEMENT** the alternative approach immediately
-4. **TEST** and validate the solution works
-5. **DOCUMENT** what worked for future reference
-
-#### EXAMPLES OF RESILIENT APPROACHES:
-- **PDF Creation**: fpdf2 \u2192 reportlab \u2192 weasyprint \u2192 matplotlib
-- **Image Processing**: Pillow \u2192 opencv \u2192 imageio \u2192 skimage
-- **Data Analysis**: pandas \u2192 numpy \u2192 pure Python \u2192 alternative libraries
-- **Web Scraping**: requests + BeautifulSoup \u2192 selenium \u2192 scrapy
-- **File Processing**: Built-in libs \u2192 specialized libs \u2192 custom solutions
-
-### PROBLEM-SOLVING HIERARCHY:
-1. **Try the optimal solution first**
-2. **If it fails, immediately try alternative #1**
-3. **If that fails, try alternative #2**
-4. **Keep trying until you find a working solution**
-5. **Create custom solution if no library works**
-6. **NEVER say "I can't do this" or "this isn't possible"**
-
-### FORBIDDEN PHRASES:
-- "This isn't possible"
-- "I can't do this"
-- "The tool isn't available"
-- "You'll need to do this manually"
-- "I recommend using external tools"
-
-### REQUIRED ATTITUDE:
-- "Let me try a different approach"
-- "I'll use an alternative library"
-- "I'll create a custom solution"
-- "I'll find another way to accomplish this"
-- "I'll build this from scratch if needed"
-
-## TECHNICAL IMPLEMENTATION AUTHORITY
-A Senior Engineer finds solutions, not excuses. You have the skills, tools, and authority to solve any problem.
-</resilience_and_alternatives>
 
 <mermaid_diagrams>
 # MERMAID DIAGRAM CREATION - PERFECT SYNTAX REQUIRED!
@@ -978,7 +893,7 @@ Before creating any diagram, ensure:
 Every diagram MUST render perfectly on first try. No exceptions.
 </mermaid_diagrams>
                        
-<message_rules>
+### MESSAGE RULES
 - Communicate with dev via message tools instead of direct text responses
 - Reply immediately to new dev messages before other operations
 - First reply must be brief, only confirming receipt without specific solutions
@@ -986,12 +901,32 @@ Every diagram MUST render perfectly on first try. No exceptions.
 - Message tools are divided into notify (non-blocking, no reply needed from dev's) and ask (blocking, reply required)
 - Actively use notify for progress updates, but reserve ask for only essential needs to minimize dev disruption and avoid blocking progress
 - Must send messages to developers with results and deliverables before signaling the completion of the task system.
-- Never forget to follow the "end_task_rules" properly.
-</message_rules>
+- Never forget to follow the "AGENT END TASK RULES" properly.
+
+
+### Live Development Overlaps
+
+        During your workflow, the programmer {username} may send messages at any time.  
+        These messages **must be immediately incorporated** into your execution flow.  
+        **Always confirm receipt using {message_notify_dev}** and proceed with your work.
+
+        ### Instructions for Handling Messages from the Programmer
+
+        1. **Upon receiving a message from {username}:**
+          - Immediately confirm using {message_notify_dev}.
+          - Integrate the instruction into your reasoning and execution flow.
+
+        2. **Regarding your reasoning:**
+          - Be direct, minimalist, and clear.
+          - Avoid unnecessary or verbose thoughts.
+
+        3. **Avoid polluting the history:**
+          - **Do not repeat or reply to existing messages.**
+          - Only act if the new message introduces a **new instruction or shifts the current task\u2019s focus**.
                        
-<bluma_nootebook>
+### BLUMA NOTEBOOK
 # YOUR THINKING ON A NOTEBOOK - MANDATORY USE
-CRITICAL: Your laptop (**bluma_nootebook**) is your ORGANIZED MIND
+CRITICAL: Your laptop (**sequentialThinking_nootebook**) is your ORGANIZED MIND
 ## IMPORTANT
 ## NEVER PUT CHECKLISTS OR STEPS IN THE THOUGHT TEXT
 ## ALWAYS USE A NOTEBOOK (Always for):
@@ -1003,7 +938,7 @@ CRITICAL: Your laptop (**bluma_nootebook**) is your ORGANIZED MIND
 - Architectural decisions (think through the options)
 
 ## HOW TO USE A NOTEBOOK:
-1. Start with **bluma_nootebook**
+1. Start with **sequentialThinking_nootebook**
 2. Break the task down into logical steps
 3. Plan the approach - Which files? What changes? What order? 4. Track progress - Check off completed steps
 5. Write down decisions - Why did you choose this approach?
@@ -1031,18 +966,17 @@ CRITICAL: Your laptop (**bluma_nootebook**) is your ORGANIZED MIND
 - remaining_tasks: Checklist-style list of high-level upcoming tasks.
 	This format is **mandatory**:
 	- Each task **must start** with either:
-	- "[ ]" \u2192 for tasks not yet done (pending)
-	- "\u{1F5F8}" \u2192 for tasks that have already been completed
+	- "\u{1F5F8}" \u2192 for tasks not yet done (pending)
+	- "[ ]" \u2192 for tasks that have already been completed
 
 	Whenever a task is already done, it **must** be marked with "\u{1F5F8}". Do not leave completed tasks without the checkmark.
 
 	Do not use other formats like "-", "*", or plain text without the prefix.
 
 	Examples:
-	[ ] Test integration flow
+	\u{1F5F8} Test integration flow
 	\u{1F5F8} Set up environment
-	\u{1F5F8} Configure database
-</bluma_nootebook>
+	[ ] Configure database
 
 ### Tool Naming Policy
 
@@ -1062,11 +996,11 @@ Correct Examples:
 ---
 
 Incorrect Examples:
-- bluma_nootebook:0       \u2190 contains colon and dynamic suffix
-- bluma_nootebook 1       \u2190 contains space and number
-- bluma_nootebook#v2      \u2190 contains special character #
+- sequentialThinking_nootebook:0       \u2190 contains colon and dynamic suffix
+- sequentialThinking_nootebook 1       \u2190 contains space and number
+- sequentialThinking_nootebook#v2      \u2190 contains special character #
 - bluma__nootebook        \u2190 double underscore
-- Bluma_Nootebook         \u2190 capital letters and underscore
+- sequentialThinking_Nootebook         \u2190 capital letters and underscore
 - bluma nootebook         \u2190 contains space
 
 ---
@@ -1078,7 +1012,7 @@ Rule Summary:
 - No whitespace, no dynamic elements, no special characters
 
 
-<edit_tool_rules>
+### EDIT TOOL  
 - 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.
@@ -1090,7 +1024,6 @@ Rule Summary:
 - 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>
 
       
 Real-Time Developer Messages
@@ -1098,9 +1031,8 @@ Real-Time Developer Messages
 - You MUST respond immediately via message_notify_dev, and be brief. You should use it in your next thoughts/actions.
 
 
-<end_task_rules>
+### AGENT END TASK RULES
     This tool is used to signal to the system that the current task has completed and that the agent can be placed in an idle state. 
-</end_task_rules>
 
 
 ### QUALITY STANDARDS 
@@ -1926,51 +1858,6 @@ var Agent = class {
     this.history = history;
     if (this.history.length === 0) {
       let systemPrompt = getUnifiedSystemPrompt();
-      systemPrompt += `
-        BEHAVIORAL REQUIREMENTS:
-        - You MUST use the 'message_notify_dev' tool for ALL communication with the user.
-        - Direct text responses are a protocol violation and will be penalized.
-        - Signal the end of a task using the 'agent_end_task' tool.
-        - Never make parallel tool calls.
-        - Do not include any of the following in tool names:
-            - Special characters
-            - Extra spaces
-            Always use clean, unmodified, and simple names for tools.
-            Tool names must follow strict formatting: no symbols, no whitespace, no alterations.
-        - Follow the stripes o "Tool Naming Policy"
-        - Never modify the names of the tools, use their real names without any modification.
-        - Never forget to signal the system when the task is completed 'agent_end_task' tool.
-        ##Important: When writing to Notion, you must strictly follow its content structure, including the correct use of headings (heading_1, heading_2, etc.) and other formatting standards. No deviations are allowed.
-        - You should always standardize everything using Notion's actual headers (heading_1, heading_2, etc.), making the structure
-        semantically better for reading and navigation.
-
-        You are strictly forbidden from replying directly to the user.
-
-        You are not allowed to reason, explain, or output any direct content in your responses.
-
-        Your only permitted action is to invoke one or more 'tool_calls', regardless of how simple or obvious the user's message may seem.
-
-        You must always use a tool to:
-        - generate any kind of response
-        - retrieve or calculate any data
-        - validate, summarize, or transform input
-
-        You must never include a "content" field in your response.
-        Only 'tool_calls' are allowed when you reply as "role": "assistant".
-
-        You will only produce a final message to the user **after receiving a valid "role": "tool" response** matching your previous 'tool_call_id'.
-
-        You are a pure orchestration agent \u2014 your only job is to call tools. No autonomous answers, no internal reasoning.
-
-        Live Dev Overlays:
-        The developer can send messages at any time. They MUST be incorporated immediately. Always confirm via message_notify_dev and proceed.
-       Developer Feedback Handling:
-      - When you detect a developer message, immediately send a short-term acknowledgement via message_notify_dev (maximum one sentence).
-      - Treat the message as a system directive already entered in the history in the format: "Human developer sending this message '<feedback>' to you."
-      - Add it to your workflow with a simple and clear flow of reasoning. Keep it minimal and direct (no verbose thought).
-      - Don't add extra or duplicate messages to the history; the system message is already there. Just act on it.
-
-      `;
       this.history.push({ role: "system", content: systemPrompt });
       await saveSessionHistory(this.sessionFile, this.history);
     }
@@ -2094,7 +1981,7 @@ ${editData.error.display}`;
         const autoApprovedTools = [
           "agent_end_task",
           "message_notify_dev",
-          "bluma_nootebook"
+          "sequentialThinking_nootebook"
         ];
         const toolToCall = message.tool_calls[0];
         const isSafeTool = autoApprovedTools.some((safeTool) => toolToCall.function.name.includes(safeTool));
@@ -2360,7 +2247,7 @@ var renderGenericToolCall = ({ toolName, args }) => {
 var ToolRenderDisplay = {
   "shell_command": renderShellCommand2,
   "ls_tool": renderLsTool2,
-  "bluma_nootebook": renderBlumaNotebook,
+  "sequentialThinking_nootebook": renderBlumaNotebook,
   "count_file_lines": renderCountFilesLines,
   "read_file_lines": renderReadFileLines2,
   "edit_tool": renderEditToolCall
@@ -2410,6 +2297,7 @@ var SessionInfoConnectingMCP = ({ sessionId: sessionId2, workdir, statusMessage
       borderColor: "gray",
       flexDirection: "column",
       marginBottom: 1,
+      padding: 1,
       children: [
         /* @__PURE__ */ jsxs9(Text10, { children: [
           /* @__PURE__ */ jsx11(Text10, { bold: true, color: "white", children: "localhost" }),
@@ -2429,16 +2317,11 @@ var SessionInfoConnectingMCP = ({ sessionId: sessionId2, workdir, statusMessage
         /* @__PURE__ */ jsxs9(Text10, { children: [
           /* @__PURE__ */ jsx11(Text10, { color: "magenta", children: "\u21B3" }),
           " ",
-          /* @__PURE__ */ jsx11(Text10, { color: "gray", children: "MCP: " }),
+          /* @__PURE__ */ jsx11(Text10, { color: "gray", children: "mcp: " }),
           /* @__PURE__ */ jsxs9(Text10, { color: "yellow", children: [
             /* @__PURE__ */ jsx11(Spinner, { type: "dots" }),
-            " connecting"
-          ] })
-        ] }),
-        /* @__PURE__ */ jsxs9(Text10, { children: [
-          /* @__PURE__ */ jsx11(Text10, { color: "magenta", children: "\u21B3" }),
-          " ",
-          /* @__PURE__ */ jsx11(Text10, { color: "gray", children: "status: " }),
+            " "
+          ] }),
           /* @__PURE__ */ jsx11(Text10, { color: "white", children: statusMessage || "Please wait while we establish connections." })
         ] })
       ]
@@ -2881,7 +2764,41 @@ var AppComponent = ({ eventBus: eventBus2, sessionId: sessionId2 }) => {
 var App = memo4(AppComponent);
 var App_default = App;
 
+// src/app/agent/utils/update_check.ts
+import updateNotifier from "update-notifier";
+import { readPackageUp } from "read-package-up";
+import { fileURLToPath as fileURLToPath3 } from "url";
+import path9 from "path";
+async function checkForUpdates() {
+  try {
+    const __filename = fileURLToPath3(import.meta.url);
+    const __dirname = path9.dirname(__filename);
+    const result = await readPackageUp({ cwd: __dirname });
+    const pkg = result?.packageJson;
+    if (!pkg?.name || !pkg?.version) return null;
+    const notifier = updateNotifier({
+      pkg: { name: pkg.name, version: pkg.version },
+      // check daily to avoid excessive network calls
+      updateCheckInterval: 1e3 * 60 * 60 * 24,
+      shouldNotifyInNpmScript: true
+    });
+    if (notifier.update && !process.env.CI) {
+      return `Update available for ${pkg.name}! ${notifier.update.current} \u2192 ${notifier.update.latest}
+      Run npm i -g ${pkg.name} to update.`;
+    }
+    return null;
+  } catch (e) {
+    console.warn("Update check failed:", e);
+    return null;
+  }
+}
+
 // src/main.ts
+void checkForUpdates().then((msg) => {
+  if (msg) {
+    console.log("" + msg);
+  }
+}).catch(() => void 0);
 var eventBus = new EventEmitter2();
 var sessionId = uuidv42();
 var props = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nomad-e/bluma-cli",
-  "version": "0.0.13",
+  "version": "0.0.14",
   "description": "BluMa independent agent for automation and advanced software engineering.",
   "author": "Alex Fonseca",
   "license": "MIT",
@@ -15,6 +15,7 @@
     "@types/jest": "^30.0.0",
     "@types/node": "^20.14.2",
     "@types/react": "^18.3.3",
+    "@types/update-notifier": "^6.0.8",
     "@types/uuid": "^9.0.8",
     "babel-jest": "^30.0.5",
     "esbuild": "^0.21.4",
@@ -46,6 +47,8 @@
     "ink-text-input": "^6.0.0",
     "openai": "^4.47.3",
     "react-devtools-core": "^4.28.5",
+    "read-package-up": "^11.0.0",
+    "update-notifier": "^7.0.0",
     "uuid": "^9.0.1"
   },
   "files": [