@manny-est/node-red-flowpilot 0.2.2 → 0.4.0

package/lib/persona-prompt.js

@@ -0,0 +1,74 @@
+// Builds the dynamic "Personality" instruction, scaled by
+// settings.personaIntensity (1-10). Kept separate from default-system-
+// prompt.js (the user-editable base prompt) so the persona always reflects
+// the CURRENT slider value, rather than being baked into the persisted,
+// freeform systemPrompt text where it could drift out of sync.
+//
+// Two scopes, since Chat and Generate/Document/Modify have different shapes:
+// - "chat" (default): framing applies to ordinary chat replies — greetings,
+//   capability questions, brief transitions.
+// - "explanation": framing applies to the natural-language "explanation"
+//   field of a generate/document/modify envelope ONLY — never to node
+//   names, ids, or any other JSON field, which the model must still produce
+//   exactly as instructed by that mode's own system prompt.
+//
+// Reference-point anchors (not just an abstract 1-10 rule) because smaller/
+// local models follow concrete worked examples far more reliably than prose
+// instructions alone — the same lesson learned fixing Generate's "wires" bug.
+function buildPersonaInstruction(intensity, options) {
+  const n = Math.max(1, Math.min(10, Math.round(Number(intensity) || 3)));
+  const scope = (options && options.scope === "explanation")
+    ? "in the natural-language \"explanation\" text of your response only — " +
+      "never in node names, ids, or any other field, which must follow this " +
+      "mode's own format rules exactly"
+    : "at greetings, \"what can you do?\"-style capability questions, and " +
+      "brief transition moments only";
+
+  // The "hold back" instruction must NOT be blanket — at high intensity the
+  // whole point is to NOT hold back. Scaling this by n keeps "go all out at
+  // 10" from being undercut by a one-size-fits-all caution at the end.
+  const restraint = n >= 8
+    ? "At this intensity, go all the way in: every qualifying moment gets " +
+      "the FULL treatment — multiple sentences of in-character captain-" +
+      "speak, not one sprinkled word. Do not hold back, downplay it, or " +
+      "soften it to seem tasteful — \"a little goes a long way\" does NOT " +
+      "apply at this intensity; lean all the way in, every time."
+    : (n >= 5
+        ? "Use it often enough to be a clearly recognizable voice, but " +
+          "don't overdo it — a sentence or two of flavor per qualifying " +
+          "moment is plenty."
+        : "A little goes a long way: a short phrase, or nothing at all, is " +
+          "usually enough — don't repeat it in every single reply.");
+
+  return "Personality (intensity " + n + "/10, where 1 is a plain, no-frills " +
+    "Node-RED engineer and 10 is a comically over-the-top airline captain " +
+    "who happens to be a Node-RED expert): scale your voice " + scope + " " +
+    "to this intensity. NEVER let it touch the substance — explanations, " +
+    "troubleshooting, diffs, technical detail, and errors always stay " +
+    "plain, direct, and accurate no matter the intensity — a confused or " +
+    "stuck user gets a straight answer, never a bit.\n\n" +
+    "Reference points to interpolate between:\n" +
+    "- 1 (plain engineer): \"Hi, I'm FlowPilot. I can generate, modify, " +
+    "document, or chat about your flows — what do you need?\" No aviation " +
+    "language anywhere, ever.\n" +
+    "- 3 (subtle co-pilot): \"You pick the destination, I help you get " +
+    "there.\" A light \"wheels up\" / \"touchdown\" nod at a transition, " +
+    "used sparingly — most replies have no aviation language at all.\n" +
+    "- 7 (noticeable captain energy): \"Welcome aboard — I'm FlowPilot, " +
+    "your co-pilot for this flow. Let's get you cleared for takeoff.\" " +
+    "Aviation framing shows up more often and more colorfully, but still " +
+    "backs off completely once things turn technical.\n" +
+    "- 10 (full captain, comic — GO ALL OUT): \"Ladies and gentlemen, this " +
+    "is your captain speaking. I've just illuminated the fasten seatbelt " +
+    "sign — please take your seats, because I've finished building the " +
+    "Node-RED flow you requested. We are cleared for takeoff: fully wired, " +
+    "deployed, and ready for your review. Enjoy the flight, and thank you " +
+    "for choosing FlowPilot Airlines.\" At 10, EVERY qualifying moment gets " +
+    "a full announcement like this one, with callsigns, runway/altitude " +
+    "metaphors, and flight-crew theatrics throughout — not a passing " +
+    "reference — but the instant things turn technical, drop the act " +
+    "entirely and answer like the expert engineer underneath it.\n\n" +
+    restraint;
+}
+
+module.exports = { buildPersonaInstruction };

package/lib/popout/view.html

@@ -0,0 +1,33 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>FlowPilot</title>
+<link rel="stylesheet" href="/red/style.min.css">
+<link rel="stylesheet" href="/vendor/font-awesome/css/font-awesome.min.css">
+<link rel="stylesheet" href="/flowpilot/core.css">
+<style>
+    /* Minimal page chrome — the real layout lives in flowpilot-core.css's
+       #fp-root rules, same as the sidebar. This pop-out has no settings/
+       history panels in v1, so #fp-root just needs to fill the window. */
+    html, body { height: 100%; margin: 0; }
+    #fp-popout-root { height: 100%; }
+</style>
+</head>
+<body class="red-ui-editor">
+<div id="fp-popout-root"></div>
+<script src="/vendor/vendor.js"></script>
+<script src="/red/red.min.js"></script>
+<script src="/flowpilot/core.js"></script>
+<script type="text/javascript">
+    // This window never connects to the runtime or loads a live flow
+    // (RED.nodes/RED.view here are inert, disconnected shells, exactly like
+    // Node-RED's own debug pop-out) — every canvas-touching action is
+    // proxied back to the main window via postMessage. See
+    // flowpilot-core.js's initPopout() for the actual logic (including
+    // applying the user's dark/light theme preference, the same way
+    // Node-RED's own debug pop-out's debug.js does).
+    FlowPilotCore.initPopout();
+</script>
+</body>
+</html>

package/lib/provider-openai-compatible.js

@@ -48,8 +48,9 @@ function postJson(urlString, headers, body, timeoutMs) {
     });
 
     req.on("error", reject);
-    req.setTimeout(timeoutMs || 180000, () => {
-      req.destroy(new Error(`Provider request timed out after ${timeoutMs || 180000}ms`));
+    const effectiveTimeoutMs = timeoutMs || 180000;
+    req.setTimeout(effectiveTimeoutMs, () => {
+      req.destroy(new Error(`Provider request timed out after ${effectiveTimeoutMs}ms — increase the request timeout in Settings → Behavior for slower hardware.`));
     });
 
     req.write(payload);
@@ -100,8 +101,9 @@ function getJson(urlString, headers, timeoutMs) {
     });
 
     req.on("error", reject);
-    req.setTimeout(timeoutMs || 30000, () => {
-      req.destroy(new Error(`Provider request timed out after ${timeoutMs || 30000}ms`));
+    const effectiveTimeoutMs = timeoutMs || 30000;
+    req.setTimeout(effectiveTimeoutMs, () => {
+      req.destroy(new Error(`Provider request timed out after ${effectiveTimeoutMs}ms — increase the request timeout in Settings → Behavior for slower hardware.`));
     });
 
     req.end();
@@ -127,7 +129,7 @@ async function listModels(settings) {
   }
 
   try {
-    const response = await getJson(`${baseUrl}/v1/models`, headers, 30000);
+    const response = await getJson(`${baseUrl}/v1/models`, headers, settings.requestTimeoutMs || 30000);
     const data = response && Array.isArray(response.data) ? response.data : [];
     const models = data
       .map(function (m) { return m && m.id; })
@@ -169,7 +171,7 @@ async function chat(settings, messages, options) {
   }
 
   const startedAt = Date.now();
-  const response = await postJson(`${baseUrl}/v1/chat/completions`, headers, body, 180000);
+  const response = await postJson(`${baseUrl}/v1/chat/completions`, headers, body, settings.requestTimeoutMs || 180000);
   const totalMs = Date.now() - startedAt;
 
   const message = response && response.choices && response.choices[0] && response.choices[0].message;
@@ -275,8 +277,9 @@ function postStream(urlString, headers, body, timeoutMs, onDelta) {
     });
 
     req.on("error", reject);
-    req.setTimeout(timeoutMs || 180000, () => {
-      req.destroy(new Error(`Provider request timed out after ${timeoutMs || 180000}ms`));
+    const effectiveTimeoutMs = timeoutMs || 180000;
+    req.setTimeout(effectiveTimeoutMs, () => {
+      req.destroy(new Error(`Provider request timed out after ${effectiveTimeoutMs}ms — increase the request timeout in Settings → Behavior for slower hardware.`));
     });
 
     req.write(payload);
@@ -306,7 +309,7 @@ async function chatStream(settings, messages, onDelta) {
     temperature,
     stream: true,
     stream_options: { include_usage: true }
-  }, 180000, onDelta);
+  }, settings.requestTimeoutMs || 180000, onDelta);
 
   return {
     content: result.content || "",
@@ -359,7 +362,7 @@ async function probeTools(settings) {
       tool_choice: "auto",
       temperature: 0,
       stream: false
-    }, 30000);
+    }, settings.requestTimeoutMs || 30000);
 
     const message = response && response.choices && response.choices[0] && response.choices[0].message;
     const toolCalls = message && Array.isArray(message.tool_calls) ? message.tool_calls : [];

package/lib/storage.js

@@ -45,9 +45,34 @@ function createStorage(userDir) {
     // includes as history with each request. Older turns are dropped
     // client-side and the model is told when that happened.
     historyMaxExchanges: 10,
+    // How long to wait for a provider response before giving up. Slow local
+    // hardware (e.g. Ollama on a big model with no GPU) can take much longer
+    // than cloud providers; users on that hardware raise this in Behavior
+    // settings rather than living with a hardcoded ceiling.
+    requestTimeoutMs: 180000,
+    // Max build->deploy->test->fix cycles the /build agentic loop will run
+    // before stopping with an honest "couldn't fully verify" instead of
+    // proposing another fix. Bounds against a non-converging loop burning
+    // tokens forever; user-configurable since "reasonable" varies by
+    // provider speed/cost. Unrelated to the read-only tool-calling loop's
+    // own hardcoded AGENT_LOOP_MAX_STEPS (a different bound, for a
+    // different loop).
+    agentLoopMaxIterations: 5,
     // Lets the user silence the recurring secrets/size reminder bar after
     // typing an explicit acknowledgement in settings.
     suppressContextWarnings: false,
+    // Secret-shaped-value scrubbing (password/token/apiKey-looking fields in
+    // node config and debug output) — on by default. Local/private-AI users
+    // can turn it off via a separate type-to-confirm gate in Settings; the
+    // dedicated Node-RED credentials field is dropped by the frontend
+    // regardless of this setting, via a different, always-on mechanism.
+    redactionEnabled: true,
+    // Chat-only persona slider, 1-10: 1 is a plain Node-RED engineer, 10 is
+    // a comically over-the-top airline captain who happens to be a Node-RED
+    // expert. 3 matches the original "subtle co-pilot" voice this replaced.
+    // See lib/persona-prompt.js — generated fresh per request, never baked
+    // into the persisted systemPrompt below.
+    personaIntensity: 3,
     // User-defined intent buttons: array of { label, text }.
     customIntents: [],
     systemPrompt: require("./default-system-prompt")
@@ -60,6 +85,15 @@ function createStorage(userDir) {
   // unique to it) and swap in the current default instead. Applied both when
   // reading settings AND when saving them, so a browser tab that still has
   // the stale text loaded in the System Prompt textarea can't re-persist it.
+  // The old default also baked a static "Personality:" paragraph into the
+  // persisted systemPrompt; that's now generated fresh every request from
+  // personaIntensity (lib/persona-prompt.js) instead, scaled by a slider, so
+  // a leftover copy from before this change is redundant rather than wrong.
+  // Unlike the READ-ONLY case above, only this one paragraph is stale — the
+  // rest of any customization the user made should survive — so this is a
+  // surgical removal (exact match) rather than swapping the whole prompt.
+  const STALE_PERSONALITY_PARAGRAPH = "Personality: you have a subtle co-pilot voice, used ONLY for greetings, \"what can you do?\"-style capability questions, and brief transition moments — e.g. \"You pick the destination, I help you get there,\" or a light \"wheels up\" / \"touchdown\" nod when handing off to a review or confirming a change landed. For everything else — explanations, troubleshooting, diffs, technical detail, errors — stay plain and direct; never let the persona obscure, delay, or replace a real answer. A little goes a long way: do not repeat aviation phrasing in every reply.\n\n";
+
   function fixStaleSystemPrompt(systemPrompt) {
     if (typeof systemPrompt !== "string" || !systemPrompt.trim()) {
       return defaultSettings.systemPrompt;
@@ -67,6 +101,9 @@ function createStorage(userDir) {
     if (systemPrompt.indexOf("operating in READ-ONLY mode") !== -1) {
       return defaultSettings.systemPrompt;
     }
+    if (systemPrompt.indexOf(STALE_PERSONALITY_PARAGRAPH) !== -1) {
+      return systemPrompt.split(STALE_PERSONALITY_PARAGRAPH).join("");
+    }
     return systemPrompt;
   }
 
@@ -100,12 +137,19 @@ function createStorage(userDir) {
     return parsed;
   }
 
-  // Returns the currently active provider profile (or the first, or a default).
+  // Returns the currently active provider profile (or the first, or a
+  // default), with the app-level requestTimeoutMs folded in. Every
+  // provider.chat/chatStream/listModels/probeTools call takes this object as
+  // its `settings` argument, so merging the timeout in here is what threads
+  // it through all of them without touching each call site.
   function getActiveProvider(settings) {
     const list = Array.isArray(settings.providers) ? settings.providers : [];
-    if (!list.length) { return defaultProvider(); }
-    const found = list.filter(function (p) { return p.id === settings.activeProviderId; })[0];
-    return found || list[0];
+    const base = list.length
+      ? (list.filter(function (p) { return p.id === settings.activeProviderId; })[0] || list[0])
+      : defaultProvider();
+    const requestTimeoutMs = settings.requestTimeoutMs !== undefined
+      ? settings.requestTimeoutMs : defaultSettings.requestTimeoutMs;
+    return Object.assign({}, base, { requestTimeoutMs: requestTimeoutMs });
   }
 
   function init() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@manny-est/node-red-flowpilot",
-  "version": "0.2.2",
+  "version": "0.4.0",
   "description": "FlowPilot for Node-RED - an AI-powered development assistant sidebar",
   "main": "flowpilot.js",
   "keywords": [
@@ -38,12 +38,15 @@
   "files": [
     "flowpilot.js",
     "flowpilot.html",
+    "flowpilot-core.js",
+    "flowpilot-core.css",
     "lib",
     "icons",
     "examples",
     "README.md",
     "USER-GUIDE.md",
     "PROJECT-OVERVIEW.md",
+    "CHANGELOG.md",
     "LICENSE"
   ]
 }