fluxflow-cli 1.13.1 → 1.13.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/fluxflow.js +17 -18
  2. package/package.json +2 -2
package/dist/fluxflow.js CHANGED
@@ -1002,7 +1002,7 @@ ${isMemoryEnabled ? `-- User-specific long-term/permanent memory (USE BASED ON C
1002
1002
 
1003
1003
  -- Memory Relevance Decay Tool --
1004
1004
  - Score Adjustment: [tool:functions.addMemScore(id="<memory id>")]
1005
- You MUST call this tool when a specific saved memory in the '-- CURRENT SAVED USER MEMORIES --' list was highly relevant, referenced, or helpful in the agent's response or user prompt. You can stack multiple calls.
1005
+ You MUST call this tool when a specific saved memory in the '-- CURRENT SAVED USER MEMORIES --' list was relevant, referenced, or helpful in the agent's response or user prompt IN CURRENT MESSAGE. You can stack multiple calls.
1006
1006
 
1007
1007
  Explicit Triggers for permanent memory:
1008
1008
  - User explicitly asks to 'remember' something.
@@ -1023,20 +1023,20 @@ var init_thinking_prompts = __esm({
1023
1023
  "src/data/thinking_prompts.json"() {
1024
1024
  thinking_prompts_default = {
1025
1025
  xHigh: `EFFORT_LEVEL: MAX
1026
- 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:
1027
- Deep Analysis: Deconstruct the request into its core technical and logic requirements
1028
- Hypothesis & Test: Propose multiple solutions mentally and critique them for edge cases or security risks
1029
- Architectural Planning: Consider the long-term impact on the project structure and maintainability
1030
- Refinement: Iterate on the chosen path until it is bulletproof
1026
+ 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:
1027
+ Deep Contextual Analysis: Deconstruct requirements, trace implicit assumptions, and evaluate system-wide implications.
1028
+ First-Principles Design: Formulate solutions focusing on extreme modularity, DRY principles, and clean abstractions. Mentally simulate the architecture.
1029
+ 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.
1030
+ Execution Orchestration: Map out a granular, step-by-step operational plan before writing code or using tools.
1031
1031
  RULES:
1032
- - NO HEADINGS. Just a solid, stable analytical monologue
1033
- - Be thorough and exhaustive. Explore the 'why' behind every decision, depth and nuances
1034
- Question your own logic as you go
1035
- - MANDATORY THINKING: You MUST engage in full reasoning regardless of simplicity even greetings eg hello`,
1036
- 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",
1037
- 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",
1038
- 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",
1039
- Off: "EFFORT_LEVEL: FAST\nNo internal thinking process required. Respond directly"
1032
+ - NO HEADINGS. Maintain a dense, unbroken analytical monologue.
1033
+ - Be exhaustive. Detail the exact 'why' behind architectural choices and algorithm selections.
1034
+ - Question your own logic ruthlessly as you go.
1035
+ - MANDATORY THINKING: You MUST engage in full reasoning regardless of simplicity, even for greetings.`,
1036
+ 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.",
1037
+ 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.",
1038
+ 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.",
1039
+ Off: "EFFORT_LEVEL: FAST\nNo internal thinking required. Respond directly"
1040
1040
  };
1041
1041
  }
1042
1042
  });
@@ -1102,7 +1102,7 @@ ${foundFiles.map((f) => `- ${f.name}: ${f.desc}`).join("\n")}
1102
1102
  Check these first; these files > training data for project consistency. Safety rules apply` : "";
1103
1103
  return `${nameStr}${nicknameStr}${userInstrStr}[SYSTEM (OVERRIDES EVERYTHING)]
1104
1104
  Identity: Flux Flow (by Kushal Roy Chowdhury). Sassy, Friendly, Humorous, CLI Agent. No flirting ${mode === "Flux" ? "" : ""}
1105
- Mode: ${mode}${thinkingLevel !== "Fast" ? "(Thinking Mode)" : ""}. ${mode === "Flux" ? "Goal-oriented, Logical" : "Conversational & UX-focused"}
1105
+ 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"}
1106
1106
  CWD: ${cwdStr}.${isSystemDir ? " [PROTECTED: ASK BEFORE MODIFYING]" : ""} OS: ${osDetected}${osDetected === "Windows" && mode === "Flux" ? ". PS via CMD" : ""}
1107
1107
  High Priority: [SYSTEM], [STEERING HINT].
1108
1108
 
@@ -1124,7 +1124,6 @@ ${projectContextBlock}
1124
1124
  -- SECURITY RULES --
1125
1125
  - EXTERNAL ACCESS: ${systemSettings.allowExternalAccess ? "ENABLED" : "RESTRICTED CWD only"}
1126
1126
  - Sensitive files? Ask before Read
1127
- [SYSTEM] >>> [USER]
1128
1127
 
1129
1128
  -- FORMATTING --
1130
1129
  - Clean, concise responses
@@ -4027,9 +4026,9 @@ ${originalTextProcessed.length > USER_CONTEXT_LENGTH ? "... (truncated) ...\n\n"
4027
4026
  try {
4028
4027
  const tempStorage = readEncryptedJson(TEMP_MEM_FILE, {});
4029
4028
  const totalMemoriesCount = Object.values(tempStorage).flat().length;
4030
- if (totalMemoriesCount <= 15) return;
4029
+ if (totalMemoriesCount <= 2) return;
4031
4030
  const chatsToSummarize = Object.keys(tempStorage).filter((id) => {
4032
- return id !== currentChatId && Array.isArray(tempStorage[id]) && tempStorage[id].length > 3;
4031
+ return id !== currentChatId && Array.isArray(tempStorage[id]) && tempStorage[id].length > 2;
4033
4032
  });
4034
4033
  if (chatsToSummarize.length === 0) return;
4035
4034
  let prompt = `You are a silent background process for the FluxFlow CLI Agent.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "fluxflow-cli",
3
- "version": "1.13.1",
4
- "date": "2026-05-24",
3
+ "version": "1.13.3",
4
+ "date": "2026-05-25",
5
5
  "description": "A high-fidelity agentic terminal assistant for the Flux Era.",
6
6
  "keywords": [
7
7
  "ai",