@manny-est/node-red-flowpilot 0.5.1 → 0.5.2

package/CHANGELOG.md

@@ -2,6 +2,85 @@
 
 All notable changes to FlowPilot are documented here.
 
+## [0.5.2] - 2026-08-04
+
+This release continues the 0.5.x line. Phase 10's agentic Modify redesign
+(WRITE-tool loop, per-call consent gates, `ask_user`) is developed
+separately and is not included here — it ships under its own beta line
+until it's ready to replace this one.
+
+### Added
+- **Anthropic provider support**: FlowPilot can now talk directly to the
+  Anthropic API (Claude models) alongside any OpenAI-compatible endpoint.
+  A new Provider Type dropdown in Settings switches between them; message
+  format, tool-call translation, and streaming (SSE) are handled
+  transparently by a dedicated adapter. Leave Base URL blank to use
+  `api.anthropic.com`.
+- **Reasoning model support**: FlowPilot detects reasoning models
+  (Nemotron, DeepSeek, QwQ, and any model returning `reasoning_content` or
+  `<think>` blocks) and shows a live collapsing "Thinking…" block during
+  streaming, or a pre-collapsed one on the agent-loop path.
+- **Auto-preflight on model change**: switching models and sending a
+  message silently probes capabilities first — no more manual "Test
+  Provider" click after every model swap.
+- **`/refresh` command**: re-renders the message panel from the in-memory
+  record store without losing conversation history — restores interactive
+  Apply buttons and review panels that went stale after a long session.
+- **Build loop — consent gates for side-effecting steps, checkpoint
+  questions, context-aware start from a selection, and an explicit
+  done/fail confirmation** instead of silently stopping.
+- **Modify — todo/plan checklist rendering**: multi-item Modify requests
+  now show a checklist that resolves as verification confirms each item
+  landed, instead of a single opaque pass/fail.
+- **Config node support**: config nodes (MQTT brokers, TLS configs, etc.)
+  are now exposed in context and can be created/connected by Modify.
+- **Server-side validator/repair layer**: malformed model output is
+  caught and, where possible, automatically repaired before it reaches
+  the canvas.
+
+### Fixed
+- **Build loop — status-only evidence false negatives**: a live, working
+  node could be declared "disconnected"/broken off a single coarse
+  node-status read, with no way to confirm otherwise. Evidence is now
+  tagged by source (`debug` vs. `status`); when only status-line evidence
+  is available and it doesn't clearly prove success or failure, the build
+  loop asks a direct yes/no confirmation instead of guessing.
+- **Modify's wire verification** read a node's stale `.wires` array
+  instead of the live link registry — a wire added earlier in the same
+  editing session could be reported as "did not land" even though it was
+  actually there. Verification now reads from `RED.nodes.eachLink`.
+- **Phantom output port on newly-created nodes**: a model-supplied
+  `wires` array that disagreed with a node type's real port count (e.g.
+  a stray empty port on a 0-output type like `http response`) rendered a
+  visible port anchor that shouldn't exist. The array length is now
+  reconciled against the node's real output count on insertion.
+- **New-node layout scatter**: the collision-avoidance grid still placed
+  two nodes at the same vertical level; switched to a single-column
+  layout (one node per row, wrap to a new column after 5 rows).
+- **`newWires` endpoint aliases**: a model response using `fromId`/`toId`
+  instead of `from`/`to` on a `newWires` entry is now repaired
+  automatically instead of both endpoints silently appearing missing.
+- **`.fp-chip-card-alt` background**: the secondary "Just add to canvas"
+  chip relied on its surrounding message bubble being dark to read as
+  part of the same chip-card family as the primary action above it —
+  bubbles follow Node-RED's light editor theme by default, so it rendered
+  as a plain white box instead.
+- Redaction round-trip poisoning, token-credential redaction gaps, and
+  several redaction echo/false-positive fixes across Modify and the build
+  loop's review step.
+- Group data corruption from a stray `changes` patch touching a group's
+  membership array directly; mixed-membership group create/extend
+  corruption.
+- Invalid port wiring (wiring to/from a port index that doesn't exist)
+  now guarded instead of silently applied.
+- New-node insertion collision avoidance tuned for faster, more reliable
+  separation on dense flows.
+- Several build-loop review false positives (metadata-field echoes,
+  debug/function/mqtt node misclassification, stale in-progress status
+  read as a real error).
+- Partial id-validation no longer discards an entire valid Modify batch
+  over one bad node id.
+
 ## [0.5.1] - 2026-07-24
 
 ### Added

package/README.md

@@ -6,9 +6,10 @@ FlowPilot: AI assistance for Node-RED, designed for builders who want help
 without giving up control.
 
 FlowPilot is an AI-powered development assistant that lives in the Node-RED
-editor sidebar. It talks to any OpenAI-compatible API (OpenAI, LocalAI,
-Ollama, etc.) and helps you generate, modify, document, and discuss your
-flows — without ever acting behind your back.
+editor sidebar. It talks natively to Anthropic (Claude models) or to any
+OpenAI-compatible API (OpenAI, LocalAI, Ollama, etc.) and helps you
+generate, modify, document, and discuss your flows — without ever acting
+behind your back.
 
 ![FlowPilot sidebar](https://github.com/manny-est/flowpilot/releases/download/v0.2.1/sidebar-chat-overview.png)
 
@@ -29,8 +30,8 @@ installation, the sidebar UI, and a chapter on every feature.
 - **Undo first** — every change goes through Node-RED's native undo
   (Ctrl+Z), including multi-part changes (insertions + rewires + new nodes)
   as a single step.
-- **Open architecture** — provider-agnostic, OpenAI-compatible REST. No
-  lock-in to one AI platform.
+- **Open architecture** — provider-agnostic: native Anthropic support, or
+  any OpenAI-compatible REST endpoint. No lock-in to one AI platform.
 - **Simple and lightweight** — favors simple, maintainable solutions over
   speculative complexity.
 
@@ -129,11 +130,24 @@ under `<node-red-userDir>/flowpilot/`:
 - `chats/` — lightweight per-session chat logs
 - `backups/` — pre-change backups
 
-## Provider setup (example: LocalAI)
+## Provider setup
 
 Open the FlowPilot sidebar, click the settings (gear) icon, and add a
-provider:
+provider.
 
+**Anthropic (Claude models):**
+
+- Provider type: `Anthropic`
+- Provider name: `Claude` (or any label)
+- Base URL: leave blank (uses `api.anthropic.com`)
+- API key: your Anthropic API key. If it returns an
+  `anthropic-workspace-id is required` error, create a new key in the
+  Anthropic Console scoped to a single workspace.
+- Model: e.g. `claude-opus-5`, or click **Refresh models**
+
+**Example: LocalAI (OpenAI-compatible):**
+
+- Provider type: `OpenAI-compatible`
 - Provider name: `LocalAI` (or any label)
 - Base URL: `http://localhost:8080`
 - API key: blank unless your instance requires one

package/USER-GUIDE.md

@@ -103,23 +103,32 @@ saved transcript permanently.
 
 ## Set a Provider
 
-FlowPilot talks to any **OpenAI-compatible** API — OpenAI itself, LocalAI,
-Ollama (with its OpenAI-compatible endpoint), LM Studio, etc.
+FlowPilot talks to **Anthropic** (Claude models) natively, or to any
+**OpenAI-compatible** API — OpenAI itself, LocalAI, Ollama (with its
+OpenAI-compatible endpoint), LM Studio, etc.
 
 1. Open **Settings** (gear icon).
 2. Under **Providers**, click **+ Add** if you need a new provider slot
    (one is created for you by default).
-3. Fill in:
-   - **Provider Name** — any label, e.g. `LocalAI` or `OpenAI`.
-   - **Base URL** — e.g. `http://localhost:8080` or `https://api.openai.com`.
-     If Node-RED is running in Docker, `localhost` refers to the *Node-RED
-     container*, not the Docker host — use the provider's container name, a
-     Docker network alias, or a host IP (e.g. `http://172.17.0.1:8080`)
-     instead.
-   - **API Key** — leave blank unless your provider requires one.
-   - **Model** — type a model name, or click **Refresh models** to fetch the
-     provider's available models (via `GET /v1/models`) and pick from the
-     list.
+3. Pick a **Provider Type**: `OpenAI-compatible` (the default) or
+   `Anthropic`.
+4. Fill in:
+   - **Provider Name** — any label, e.g. `LocalAI`, `OpenAI`, or `Claude`.
+   - **Base URL** —
+     - OpenAI-compatible: e.g. `http://localhost:8080` or
+       `https://api.openai.com`. If Node-RED is running in Docker,
+       `localhost` refers to the *Node-RED container*, not the Docker
+       host — use the provider's container name, a Docker network alias,
+       or a host IP (e.g. `http://172.17.0.1:8080`) instead.
+     - Anthropic: leave blank to use `api.anthropic.com` — only set this
+       if you're routing through a proxy or gateway.
+   - **API Key** — for OpenAI-compatible, leave blank unless your provider
+     requires one. For Anthropic, this is required. If your key returns
+     an `anthropic-workspace-id is required` error, it wasn't scoped to a
+     single workspace when created — go to the Anthropic Console, create a
+     new key, and choose a specific workspace at creation time.
+   - **Model** — type a model name, or click **Refresh models** to fetch
+     the provider's available models and pick from the list.
    - **Temperature** — a starting value of `0.2` works well for most uses.
 
 ![Provider settings: Base URL, API key, model, and temperature fields](https://github.com/manny-est/flowpilot/releases/download/v0.2.1/sidebar-settings-providers.png)

package/flowpilot-core.css

@@ -15,6 +15,7 @@
 
 .fp-header-row {
     display: flex;
+    flex-wrap: wrap;
     align-items: center;
     gap: 12px;
 }
@@ -49,8 +50,12 @@
 .fp-view-buttons {
     display: flex;
     gap: 6px;
-    position: relative;
-    top: 2px;
+    /* Own row below the logo/title/subtitle at default (narrow) sidebar
+       width — sharing the row with .fp-heading left too little space for
+       "AI flow assistant" to fit on one line, so it wrapped across three. */
+    flex: 1 0 100%;
+    justify-content: flex-end;
+    margin-top: 8px;
 }
 
 .fp-panel {
@@ -366,6 +371,81 @@
     font-size: 16px;
 }
 
+/* Secondary/escape-hatch variant: muted dark background, muted text.
+   Same hover glow as fp-chip-card so it reads as part of the same family
+   without competing visually with the primary action above it. Explicit
+   background, not transparent — .fp-message's surrounding bubble follows
+   Node-RED's light editor theme variable by default, so "transparent"
+   showed through as plain white instead of blending into a dark parent
+   that doesn't actually exist. */
+.fp-chip-card.fp-chip-card-alt {
+    background: #171e25;
+    border-color: #2a333c;
+    color: #8a96a3;
+}
+.fp-chip-card.fp-chip-card-alt .fp-chip-title {
+    color: #8a96a3;
+    font-weight: 500;
+}
+.fp-chip-card.fp-chip-card-alt:hover {
+    border-color: #46d39a;
+    box-shadow: inset 0 1px 0 rgba(255, 255, 255, 0.05), 0 0 0 1px #46d39a, 0 0 14px -2px #46d39a;
+    color: #dfe6ee;
+}
+.fp-chip-card.fp-chip-card-alt:hover .fp-chip-title {
+    color: #fff;
+}
+.fp-chip-card.fp-chip-card-alt .fp-chip-go {
+    color: #4a5662;
+}
+.fp-chip-card.fp-chip-card-alt:hover .fp-chip-go {
+    color: #46d39a;
+}
+
+/* WS4 build consent gate (Proceed/Skip): sits inline in a question-row,
+   side by side, so it stays .fp-chip-card's compact pill-shaped sibling
+   rather than that pattern's full-width stacked card layout. Reuses the
+   same cockpit accent/muted color language so both read as one family. */
+.fp-consent-chip {
+    display: inline-flex;
+    align-items: center;
+    padding: 6px 14px;
+    border-radius: 999px;
+    font-size: 12.5px;
+    font-weight: 600;
+    cursor: pointer;
+    white-space: nowrap;
+    background: #141a21;
+    border: 1px solid #2c3742;
+    color: #dfe6ee;
+    transition: border-color .12s ease, box-shadow .12s ease;
+}
+
+.fp-consent-chip:hover:not(:disabled) {
+    border-color: #46d39a;
+    box-shadow: 0 0 0 1px #46d39a, 0 0 10px -2px #46d39a;
+}
+
+.fp-consent-chip:active:not(:disabled) {
+    transform: translateY(1px);
+}
+
+.fp-consent-chip:disabled {
+    cursor: default;
+    opacity: 0.75;
+}
+
+.fp-consent-chip-primary {
+    border-color: rgba(70, 211, 154, 0.35);
+    color: #46d39a;
+}
+
+.fp-consent-chip-alt {
+    background: transparent;
+    border-color: #2a333c;
+    color: #8a96a3;
+}
+
 .fp-chip-hint {
     margin-top: 4px;
     font-size: 12px;
@@ -596,6 +676,52 @@
     justify-content: flex-end;
 }
 
+/* W4 todo spine. Single-item plans render as a status line (.fp-todo-status);
+   multi-item plans render as a card (.fp-todo-card) with a checklist inside. */
+.fp-todo-status {
+    display: inline-block;
+    font-size: 12px;
+    padding: 3px 10px;
+    margin: 0 0 4px 0;
+    border-radius: 12px;
+    max-width: 100%;
+    overflow: hidden;
+    text-overflow: ellipsis;
+    white-space: nowrap;
+}
+.fp-todo-pending, .fp-todo-active {
+    background: var(--red-ui-secondary-background, #eee);
+    color: var(--red-ui-secondary-text-color, #888);
+}
+.fp-todo-done {
+    background: rgba(34, 139, 34, 0.12);
+    color: #1a7a1a;
+}
+.fp-todo-failed {
+    background: rgba(200, 40, 40, 0.10);
+    color: #b22222;
+}
+.fp-todo-card {
+    padding: 6px 10px;
+    margin: 0 0 4px 0;
+    background: var(--red-ui-secondary-background, #eee);
+    border-radius: 6px;
+    font-size: 13px;
+}
+.fp-todo-list {
+    list-style: none;
+    padding: 0;
+    margin: 0;
+}
+.fp-todo-item {
+    padding: 1px 0;
+    line-height: 1.5;
+}
+.fp-todo-item-pending { color: var(--red-ui-secondary-text-color, #999); }
+.fp-todo-item-active  { font-weight: 600; color: var(--red-ui-text-color, #333); }
+.fp-todo-item-done    { color: #1a7a1a; }
+.fp-todo-item-failed  { color: #b22222; }
+
 .fp-json-toolbar {
     display: flex;
     justify-content: flex-end;