Back to the changelog

v0.23.5

June 9, 2026

Smarter item search in the Flow Agent, consistent errors between REST and MCP, plus interface fixes

  • Improvement

    Flow Agent: smarter item search

    The Flow Agent (and the MCP server) item search now matches **partial text**, **case-insensitively**: searching *"demo fs"* finds the item «DEMO FS NUOVO - Documenti Google». Before, only the **exact** reference worked, so searching by part of the name always failed. The search now looks at both the **title** shown to the user and the **entity reference**, and returns the title so the agent shows the right name.

  • Improvement

    Flow Agent: less confusion between "new item" and "new flow"

    The assistant now **clearly distinguishes** a request to create a **new item** (on an existing flow) from creating a **new flow**. Phrases like *"create a new one"* no longer mistakenly start the creation of a flow that already exists. Before proposing to create a new flow, the agent **checks whether one already exists** with that name. And if a search returns nothing on the first try, it **retries with fewer words** instead of immediately declaring the item does not exist.

  • Integration

    More consistent errors between REST API and MCP

    When an operation via **MCP** fails for a business rule (e.g. *"blocking task pending"*, missing required fields, item not found), the call is now marked as a **structured error** instead of returning a false "success" with the error hidden in the content. This aligns MCP behavior with the REST API and makes integrations (n8n, AI assistants) that need to tell success from failure much more reliable.

  • Design

    Interface fixes

    **Site icon (favicon)**: fixed the 404 console errors for missing icons; there is now a dedicated FlowSharp icon that shows correctly in the browser tab. **Settings → Organization**: the fields (Company name, Email, Phone, etc.) are now **properly linked to their labels** with correct identifiers and autocomplete types — improving accessibility and browser autofill. **"Save" button**: when disabled (no changes to save) it now looks **clearly non-clickable**, instead of still appearing as an active button.