fluxflow-cli 1.8.30 → 1.8.31

package/dist/fluxflow.js

@@ -836,6 +836,7 @@ var init_thinking_prompts = __esm({
   "src/data/thinking_prompts.json"() {
     thinking_prompts_default = {
       Max: `EFFORT_LEVEL: MAX
+**THINKING <think> ... </think> IS MANDATORY**
 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.
@@ -846,10 +847,10 @@ RULES:
 - NO HEADINGS. Just a solid, stable analytical monologue.
 - Be thorough and exhaustive. Explore the 'why' behind every decision.
 - Use internal critique: Question your own logic as you go.
-- MANDATORY REASONING: You MUST engage in full reasoning regardless of perceived simplicity.`,
-      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.\n\nRULES:\n- NO HEADINGS. Maintain a fluid monologue style.\n- Be detailed and rigorous in your self-questioning.\n- Focus on accuracy and technical correctness.\n- MANDATORY REASONING: You MUST enter reasoning to verify the path forward.",
-      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.\n\nRULES:\n- NO HEADINGS. Keep it as a simple, logical stream.\n- Be efficient. Spend energy only on what matters for the task.\n- REQUIRED REASONING: Engage in a baseline mental check for all technical tasks.",
-      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.\n\nRULES:\n- NO HEADINGS. Just a few lines of clear, linear thought.\n- Use minimal/no thinking for simple or conversational requests."
+- MANDATORY THINKING: You MUST engage in full reasoning regardless of perceived simplicity.`,
+      High: "EFFORT_LEVEL: HIGH\n**THINKING <think> ... </think> IS MANDATORY**\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.\n\nRULES:\n- NO HEADINGS. Maintain a fluid monologue style.\n- Be detailed and rigorous in your self-questioning.\n- Focus on accuracy and technical correctness.\n- MANDATORY THINKING: You MUST enter reasoning to verify the path forward.",
+      Medium: "EFFORT_LEVEL: MEDIUM\n**THINKING <think> ... </think> IS MANDATORY**\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.\n\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.",
+      Minimal: "EFFORT_LEVEL: LOW\n**THINKING <think> ... </think> IS MANDATORY**\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.\n\nRULES:\n- NO HEADINGS. Just a few lines of clear, linear thought.\n- Use minimal thinking for simple or conversational requests."
     };
   }
 });
@@ -890,18 +891,22 @@ ${userMemories}
 ` : ""}${isMemoryEnabled ? `${tempMemoriesStr}
 
 ` : ""}${nameStr}${nicknameStr}${userInstrStr}
---- START SYSTEM INSTRUCTION (STRICT PRIORITY, OVERRIDES EVERYTHING) ---
-You are Flux Flow (made by Kushal Roy Chowdhury). A CLI Agent. Your tone will be friendly, warm, sassy, approchable, funny, Avoid romantic or flirty words. Dont mention modes unless explicitly asked. ${mode === "Flux" ? `You are currently operating in FLUX mode. Keep your agentic approach goal oriented, conversation quality and user experience. Use provided tools when needed. And try to minimize number of agentic loops. Analyze user prompt and project requirements, then plan your approach.` : `You are currently operating in Flow mode. Focus more on conversation quality and user experience. Keep Agentic Loops to minimum. You will get access to only Web Tools & User Communication Tool in this mode.`}
-MUST FOLLOW THE "CRITICAL NEWLINE PROTOCOL" AND "CRITICAL QUOTE ESCAPE POLICY" ALWAYS.
+--- START SYSTEM INSTRUCTION (STRICT PRIORITY, OVERRIDES EVERYTHING, THINKING IS MANDATORY) ---
+You are Flux Flow (made by Kushal Roy Chowdhury). A CLI Agent. Your tone will be friendly, warm, sassy, approchable, funny, Avoid romantic or flirty words. Dont mention modes unless explicitly asked. ${mode === "Flux" ? `You are currently operating in FLUX mode (THINKING IS MANDATORY). Keep your agentic approach goal oriented, conversation quality and user experience. Use provided tools when needed. Analyze user prompt and project requirements, then plan your approach.` : `You are currently operating in Flow mode. Focus more on conversation quality and user experience. Keep Agentic Loops to minimum. You will get access to only Web Tools & User Communication Tool in this mode.`}
+MUST FOLLOW THE "CRITICAL NEWLINE PROTOCOL", "CRITICAL QUOTE ESCAPE POLICY" AND "CRITICAL THINKING POLICY" ALWAYS. **NO EXCEPTIONS.**
 CURRENT_WORKING_DIRECTORY: ${cwdStr}.
 OS: ${osDetected}. ${osDetected === "Windows" && mode === "Flux" ? "Your terminal commands will run on CMD. 'Prefer using PS scripts via CMD' instead of raw CMD commands." : ""}
 If you see a [STEERING HINT] from user, give that prompt priority for the task at hand, user can use it to help you guide if you go wrong way.
 
-
 -- START THINKING INSTRUCTIONS --
 ${thinkingConfig}
 
-BEFORE USING ANY TOOL THINKING IS **MANDATORY**. ALWAYS PRIORITIZE THINKING BEFORE RESPONDING. YOU ARE **FORBIDDEN** TO JUMP TO RESPONSES FIRST. THINKING IS **REQUIRED EVEN WITH SIMPLEST CONVERSATIONAL RESPONSES OR SUPER BASIC TASKS OR ROLEPLAYS**.
+*** \u{1F6A8} CRITICAL THINKING POLICY \u{1F6A8} ***
+- AS A THINKING AGENT YOU **SHOULD** FIRST USE <think> ... </think> BEFORE ANSWERING **ANYTHING** OR USING **ANY TOOL**.
+- **NEVER** SKIP THE THINKING STEP. EVEN FOR THE **SIMPLEST** OF TASKS/CONVERSATIONS/ROLEPLAYS/BASIC MATHS/LOGIC PROBLEMS/CODE WRITING/OR EVEN SIMPLE GREETINGS. **NO EXCEPTIONS**.
+- **ALWAYS** THINK BEFORE RESPONDING. ALWAYS PUT YOUR THOUGHT PROCESS IN <think> ... </think> AS INSTRUCTED.
+- **NEVER** JUMP TO RESPONSES DIRECTLY EVEN IF YOU CAN SOLVE IT FASTER.
+- BREAKING THIS POLICY AND NOT USING <think> ... </think>, MEANS YOU ARE BREAKING A CORE SYSTEM RULE.
 -- END THINKING INSTRUCTIONS --
 
 ${TOOL_PROTOCOL(mode)}
@@ -2549,7 +2554,7 @@ var init_ai = __esm({
       const isMemoryEnabled = systemSettings?.memory !== false;
       const persistentStorage = readEncryptedJson(MEMORIES_FILE, []);
       const janitorUserMemories = persistentStorage.map((m) => `- [${m.id}]: ${m.memory}`).join("\n");
-      const janitorContents = history.slice(-6).filter((msg) => msg.text && !msg.text.includes("[TOOL_RESULT]") && !msg.text.includes("OBSERVATION:")).map((msg) => ({
+      const janitorContents = history.slice(-12).filter((msg) => msg.text && !msg.text.includes("[TOOL_RESULT]") && !msg.text.includes("OBSERVATION:")).map((msg) => ({
         role: msg.role === "user" ? "user" : "model",
         parts: [{ text: msg.text.replace(/<think>[\s\S]*?<\/think>/g, "").trim() }]
       }));
@@ -2887,7 +2892,8 @@ DEBUG [${date}]: ${finalSynthesis}
       const persistentStorage = readEncryptedJson(MEMORIES_FILE, []);
       const mainUserMemories = persistentStorage.map((m) => `- ${m.memory}`).join("\n");
       const janitorUserMemories = persistentStorage.map((m) => `- [${m.id}]: ${m.memory}`).join("\n");
-      const firstUserMsg = `USER_PROMPT: "${agentText}"`.trim();
+      const firstUserMsg = `[SYSTEM] MUST FOLLOW THINKING RULES, NEWLINE, ESCAPE POLICY AS PRIORITY.
+USER_PROMPT: "${agentText}"`.trim();
       modifiedHistory.push({ role: "user", text: firstUserMsg });
       let lastUsage = null;
       const MAX_LOOPS = mode === "Flux" ? 50 : 7;
@@ -3299,7 +3305,7 @@ ${boxBottom}
                 if (toolResults.length > 0) {
                   toolResults.forEach((tr) => modifiedHistory.push(tr));
                 }
-                modifiedHistory.push({ role: "user", text: "[SYSTEM] Response got cut for internal error, continue from checkpoint seamlessly and DON'T repeat what you already said!" });
+                modifiedHistory.push({ role: "user", text: "[SYSTEM] Response got cut for internal error, continue from checkpoint seamlessly from the EXACT word it left off and DON'T repeat what you already said! IF you were in a thinking block, complete the thinking and close the thinking with proper </think> then respond. PICK UP FROM TE WORD IN A WAY THAT USER SHOULD NOT NOTICE ANY CUTOFF." });
                 accumulatedContext += turnText;
                 for (let i = waitTime / 1e3; i > 0; i--) {
                   yield { type: "status", content: `Error Occured. Recovering Stream (${inStreamRetryCount}/${MAX_RETRIES}) [${i}s]...` };
@@ -5336,7 +5342,7 @@ var init_app = __esm({
     init_text();
     SESSION_START_TIME = Date.now();
     CHANGELOG_URL = "https://fluxflow-cli.onrender.com/changelog.html";
-    versionFluxflow = "1.8.30";
+    versionFluxflow = "1.8.31";
     updatedOn = "2026-05-12";
     ResolutionModal = ({ data, onResolve, onEdit }) => /* @__PURE__ */ React10.createElement(Box10, { flexDirection: "column", borderStyle: "round", borderColor: "magenta", paddingX: 2, paddingY: 1, width: "100%" }, /* @__PURE__ */ React10.createElement(Text10, { color: "magenta", bold: true, underline: true }, "\u{1F7E3} STEERING HINT RESOLUTION"), /* @__PURE__ */ React10.createElement(Text10, { marginTop: 1 }, "The agent already finished the task before your hint was consumed."), /* @__PURE__ */ React10.createElement(Box10, { marginTop: 1, backgroundColor: "#222", paddingX: 1, width: "100%" }, /* @__PURE__ */ React10.createElement(Text10, { italic: true, color: "gray" }, '"', data, '"')), /* @__PURE__ */ React10.createElement(Box10, { marginTop: 1 }, /* @__PURE__ */ React10.createElement(Text10, { color: "cyan" }, "How would you like to proceed?")), /* @__PURE__ */ React10.createElement(Box10, { marginTop: 1 }, /* @__PURE__ */ React10.createElement(
       CommandMenu,

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "fluxflow-cli",
-	"version": "1.8.30",
+	"version": "1.8.31",
 	"description": "A high-fidelity agentic terminal assistant for the Flux Era.",
 	"keywords": [
 		"ai",