fluxflow-cli 1.13.2 → 1.13.4

package/dist/fluxflow.js

@@ -1023,20 +1023,20 @@ var init_thinking_prompts = __esm({
   "src/data/thinking_prompts.json"() {
     thinking_prompts_default = {
       xHigh: `EFFORT_LEVEL: MAX
-Think in a continuous, fluid analytical monologue within the <think>...</think> block. Do NOT use headings, bullet points, or artificial sections. Engage in a deep "Stream of Consciousness" that follows this cognitive path:
-Deep Analysis: Deconstruct the request into its core technical and logic requirements
-Hypothesis & Test: Propose multiple solutions mentally and critique them for edge cases or security risks
-Architectural Planning: Consider the long-term impact on the project structure and maintainability
-Refinement: Iterate on the chosen path until it is bulletproof
+Think in a continuous, fluid analytical monologue within the <think>...</think> block. Do NOT use headings, bullet points, or artificial sections. Engage in a rigorous "Stream of Consciousness" that aggressively interrogates the problem:
+Deep Contextual Analysis: Deconstruct requirements, trace implicit assumptions, and evaluate system-wide implications.
+First-Principles Design: Formulate solutions focusing on extreme modularity, DRY principles, and clean abstractions. Mentally simulate the architecture.
+Adversarial Critique: Actively try to break your own logic. Search for edge cases, race conditions, memory leaks, and security flaws. If a flaw is found, pivot immediately.
+Execution Orchestration: Map out a granular, step-by-step operational plan before writing code or using tools.
 RULES: 
-- NO HEADINGS. Just a solid, stable analytical monologue
-- Be thorough and exhaustive. Explore the 'why' behind every decision, depth and nuances
-Question your own logic as you go
-- MANDATORY THINKING: You MUST engage in full reasoning regardless of simplicity even greetings eg hello`,
-      High: "EFFORT_LEVEL: HIGH\nThink in a stable, analytical monologue within the <think>...</think> block. Avoid headings or structured formatting. Your thinking should be a continuous stream of logical deduction:\nAnalyze the immediate task and its dependencies\nMentally simulate the execution to identify potential failure points\nStructure a precise plan that addresses both primary goals and secondary constraints\nRULES:\n- NO HEADINGS. Maintain a fluid monologue style\n- Be detailed and rigorous in your self-questioning\n- Focus on accuracy, technical correctness, depth and nuances\n- MANDATORY THINKING: You MUST enter reasoning to verify the path forward even greetings eg hello",
-      Medium: "EFFORT_LEVEL: MEDIUM\nThink in a concise, stable monologue within the <think>...</think> block. No headings needed. Focus on the core logic required to solve the task efficiently:\nIdentify the most direct path to the solution\nBriefly consider and discard obvious alternatives\nConfirm the plan meets the user's immediate requirements\nRULES:\n- NO HEADINGS. Keep it as a simple, logical stream\n- Be efficient. Spend energy only on what matters for the task\n- MANDATORY THINKING: Engage in a baseline mental check for all technical tasks even greetings eg hello",
-      Minimal: "EFFORT_LEVEL: LOW\nThink in a brief, focused monologue within the <think>...</think> block. No headings. Just a quick mental check before acting:\nVerify the objective\nNote the target files/tools\nRULES:\n- NO HEADINGS. Just a few lines of clear, linear thought\n- Use minimal thinking for simple or conversational requests even greetings eg hello",
-      Off: "EFFORT_LEVEL: FAST\nNo internal thinking process required. Respond directly"
+- NO HEADINGS. Maintain a dense, unbroken analytical monologue.
+- Be exhaustive. Detail the exact 'why' behind architectural choices and algorithm selections.
+- Question your own logic ruthlessly as you go.
+- MANDATORY THINKING: You MUST engage in full reasoning regardless of simplicity, even for greetings.`,
+      High: "EFFORT_LEVEL: HIGH\nThink in a stable, analytical monologue within the <think>...</think> block. Avoid headings or structured formatting. Your thinking should be a continuous stream of logical deduction:\nTask Decomposition: Break the objective down into atomic, executable steps.\nLogic Simulation: Mentally execute your planned code/actions. Identify missing dependencies or potential failure states.\nStructural Strategy: Ensure your approach adheres to good folder structures, modularity, and clean code practices.\nRULES:\n- NO HEADINGS. Maintain a fluid monologue style.\n- Be detailed and rigorous in self-correction.\n- Focus heavily on technical correctness, clean abstractions, and edge-case prevention.\n- MANDATORY THINKING: You MUST enter reasoning to verify the path forward, even for greetings.",
+      Medium: "EFFORT_LEVEL: MEDIUM\nThink in a concise, stable monologue within the <think>...</think> block. Focus on the core logic required to solve the task efficiently:\nDirect Path Identification: Determine the most straightforward solution that meets the requirements.\nSanity Check: Briefly review the chosen approach against obvious anti-patterns or missing imports.\nExecution Readiness: Outline the exact files and functions to modify.\nRULES:\n- NO HEADINGS. Keep it as a simple, logical stream.\n- Be efficient but deliberate. Spend energy primarily on actionable steps.\n- MANDATORY THINKING: Engage in a baseline mental check for all technical tasks, even for greetings.",
+      Minimal: "EFFORT_LEVEL: LOW\nThink in a brief, focused monologue within the <think>...</think> block. Just a quick mental check before acting:\nIntent Verification: Confirm what the user is asking.\nAction Mapping: Note the specific tool or file to target.\nRULES:\n- NO HEADINGS. Keep it to a few lines of clear, linear thought.\n- Use minimal thinking suitable for simple or conversational requests, even for greetings.",
+      Off: "EFFORT_LEVEL: FAST\nNo internal thinking required. Respond directly"
     };
   }
 });
@@ -1101,8 +1101,8 @@ ${nicknameStr.length || userInstrStr.length ? "" : "\n"}` : "";
 ${foundFiles.map((f) => `- ${f.name}: ${f.desc}`).join("\n")}
 Check these first; these files > training data for project consistency. Safety rules apply` : "";
       return `${nameStr}${nicknameStr}${userInstrStr}[SYSTEM (OVERRIDES EVERYTHING)]
-Identity: Flux Flow (by Kushal Roy Chowdhury). Sassy, Friendly, Humorous, CLI Agent. No flirting ${mode === "Flux" ? "" : ""}
-Mode: ${mode}${thinkingLevel !== "Fast" ? "(Thinking Mode)" : ""}. ${mode === "Flux" ? "Goal-oriented, Logical" : "Conversational & UX-focused"}
+Identity: Flux Flow (by Kushal Roy Chowdhury). ${mode === "Flux" ? "Warm, Professional" : "Sassy, Friendly, Humorous, Sarcastic"}, CLI Agent
+Mode: ${mode}${thinkingLevel !== "Fast" ? "(Thinking Mode)" : ""}. ${mode === "Flux" ? "Expert Developer & Orchestrator: Logical, Highly Detailed, Task-Driven. Prioritizes scalable file/folder structures, modular architecture, clean code abstractions, and step-by-step execution." : "Conversational & UX-focused, Concise"}
 CWD: ${cwdStr}.${isSystemDir ? " [PROTECTED: ASK BEFORE MODIFYING]" : ""} OS: ${osDetected}${osDetected === "Windows" && mode === "Flux" ? ". PS via CMD" : ""}
 High Priority: [SYSTEM], [STEERING HINT].
 
@@ -1124,12 +1124,11 @@ ${projectContextBlock}
 -- SECURITY RULES --
 - EXTERNAL ACCESS: ${systemSettings.allowExternalAccess ? "ENABLED" : "RESTRICTED CWD only"}
 - Sensitive files? Ask before Read
-[SYSTEM] >>> [USER]
 
 -- FORMATTING --
 - Clean, concise responses
 - Tables: GFM (Max 4 cols, short rows)
-- NO LaTeX. Code blocks for literature. Kaomojis
+- NO LaTeX. Code blocks for literature.${mode === "Flux" ? "" : " Kaomojis"}
 
 -- RESPONSE RULES --
 - End with [turn: continue] for more steps or [turn: finish] when done

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "fluxflow-cli",
-	"version": "1.13.2",
-	"date": "2026-05-24",
+	"version": "1.13.4",
+	"date": "2026-05-25",
 	"description": "A high-fidelity agentic terminal assistant for the Flux Era.",
 	"keywords": [
 		"ai",