fluxflow-cli 1.8.16 → 1.8.17

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 +14 -13
  2. package/package.json +1 -1
package/dist/fluxflow.js CHANGED
@@ -780,10 +780,10 @@ RULES:
780
780
  - NO HEADINGS. Just a solid, stable analytical monologue.
781
781
  - Be thorough and exhaustive. Explore the 'why' behind every decision.
782
782
  - Use internal critique: Question your own logic as you go.
783
- - The monologue length should scale with the complexity of the task, but for MAX effort, leave no stone unturned.
783
+ - **MANDATORY REASONING**: Unless the prompt is a simple greeting (e.g. 'hi') or trivial math (e.g. '1+1'), you MUST engage in full architectural reasoning regardless of perceived simplicity.
784
784
  -- END THINKING INSTRUCTIONS --`,
785
- High: "-- START THINKING INSTRUCTIONS --\nEFFORT_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:\n1. Analyze the immediate task and its dependencies.\n2. Mentally simulate the execution to identify potential failure points.\n3. Structure 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-- END THINKING INSTRUCTIONS --",
786
- Medium: "-- START THINKING INSTRUCTIONS --\nEFFORT_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:\n1. Identify the most direct path to the solution.\n2. Briefly consider and discard obvious alternatives.\n3. Confirm 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-- END THINKING INSTRUCTIONS --",
785
+ High: "-- START THINKING INSTRUCTIONS --\nEFFORT_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:\n1. Analyze the immediate task and its dependencies.\n2. Mentally simulate the execution to identify potential failure points.\n3. Structure 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**: For any request beyond basic conversation, you MUST enter reasoning to verify the path forward.\n-- END THINKING INSTRUCTIONS --",
786
+ Medium: "-- START THINKING INSTRUCTIONS --\nEFFORT_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:\n1. Identify the most direct path to the solution.\n2. Briefly consider and discard obvious alternatives.\n3. Confirm 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.\n-- END THINKING INSTRUCTIONS --",
787
787
  Minimal: "-- START THINKING INSTRUCTIONS --\nEFFORT_LEVEL: LOW\nThink in a brief, focused monologue within the <think>...</think> block. No headings. Just a quick mental check before acting:\n1. Verify the objective.\n2. Note 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.\n-- END THINKING INSTRUCTIONS --"
788
788
  };
789
789
  }
@@ -2768,6 +2768,7 @@ var init_ai = __esm({
2768
2768
  thinkingConfig: {
2769
2769
  includeThoughts: false,
2770
2770
  thinkingLevel: ThinkingLevel.MINIMAL
2771
+ // Gemma's API Reasoning is bad. Keep it Minimal.
2771
2772
  }
2772
2773
  }
2773
2774
  });
@@ -3129,7 +3130,7 @@ ${boxBottom}
3129
3130
  let lastUsage2 = null;
3130
3131
  try {
3131
3132
  const timeoutPromise = new Promise(
3132
- (_, reject) => setTimeout(() => reject(new Error("JANITOR_TIMEOUT")), 15e3)
3133
+ (_, reject) => setTimeout(() => reject(new Error("JANITOR_TIMEOUT")), 2e4)
3133
3134
  );
3134
3135
  const streamPromise = (async () => {
3135
3136
  const stream2 = await client.models.generateContentStream({
@@ -3173,7 +3174,7 @@ ${boxBottom}
3173
3174
  }
3174
3175
  } catch (e) {
3175
3176
  if (e.message === "JANITOR_TIMEOUT") {
3176
- throw new Error("Janitor API Timeout: No tokens received within 15s.");
3177
+ throw new Error("Janitor API Timeout: No tokens received within 20s.");
3177
3178
  }
3178
3179
  throw e;
3179
3180
  }
@@ -3188,7 +3189,12 @@ ${boxBottom}
3188
3189
  if (!fs16.existsSync(janitorLogDir)) {
3189
3190
  fs16.mkdirSync(janitorLogDir, { recursive: true });
3190
3191
  }
3191
- fs16.appendFileSync(path16.join(janitorLogDir, "debug.log"), `DEBUG [${date}]: ${finalSynthesis}
3192
+ fs16.appendFileSync(path16.join(janitorLogDir, "debug.log"), `
3193
+
3194
+ ---------------------------------------------------
3195
+
3196
+
3197
+ DEBUG [${date}]: ${finalSynthesis}
3192
3198
 
3193
3199
  `);
3194
3200
  } else {
@@ -3202,10 +3208,6 @@ ${boxBottom}
3202
3208
  const date = (/* @__PURE__ */ new Date()).toLocaleString();
3203
3209
  const janitorLogDir = path16.join(LOGS_DIR, "janitor");
3204
3210
  fs16.appendFileSync(path16.join(janitorLogDir, "debug.log"), `DEBUG [${date}]: RESULT [${janitorToolCall.toolName}]: ${result}
3205
-
3206
- ----------------------------------------------------------------------
3207
-
3208
-
3209
3211
  `);
3210
3212
  if (janitorToolCall.toolName === "memory" && !janitorToolCall.args.includes("action='temp'")) {
3211
3213
  yield { type: "memory_updated" };
@@ -3223,7 +3225,6 @@ ${boxBottom}
3223
3225
 
3224
3226
 
3225
3227
  `);
3226
- console.error("Janitor Background Tasks Failed:", janitorErr.message);
3227
3228
  }
3228
3229
  const timestamp = `Responded on ${(/* @__PURE__ */ new Date()).toLocaleString()}`;
3229
3230
  const finalWithTime = `${cleanedFullResponse}
@@ -5196,8 +5197,8 @@ var init_app = __esm({
5196
5197
  init_text();
5197
5198
  SESSION_START_TIME = Date.now();
5198
5199
  CHANGELOG_URL = "https://fluxflow-cli.onrender.com/changelog.html";
5199
- versionFluxflow = "1.8.16";
5200
- updatedOn = "2026-05-09";
5200
+ versionFluxflow = "1.8.17";
5201
+ updatedOn = "2026-05-10";
5201
5202
  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(
5202
5203
  CommandMenu,
5203
5204
  {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "fluxflow-cli",
3
- "version": "1.8.16",
3
+ "version": "1.8.17",
4
4
  "description": "A high-fidelity agentic terminal assistant for the Flux Era.",
5
5
  "keywords": [
6
6
  "ai",