Back to the changelog

v0.83.0

August 13, 2026

Flows without hidden dead ends, operational recovery under control. The designer blocks processes that cannot reach a final state, automation stalls become visible alerts, cross-install invitations survive retries and crashes, Admins can recover an item through MCP, and the extension downloads preconfigured from Settings.

  • Improvement

    The designer sees real exit routes

    Before publishing, FlowSharp checks the routes the engine can actually take. An unreachable final state, a cycle with no exit, or an Auto/AI state without a fallback is reported directly on the design with clear remediation.

  • Improvement

    Automation stalls become actionable

    If an item stops because no rule matches or an AI execution fails, a persistent Admin alert is created. Moving the item resolves it; in Process Map it remains distinct from the ordinary statistical stall indicator.

  • Security

    Federation invites resilient to replay and forwarded links

    The invitation token is handed to the HOME backend and immediately removed from the URL. A short-lived intent, verified email, and replay key make double clicks, timeouts, and crashes safe without reopening the old cross-origin flow.

  • Integration

    Administrative MCP break-glass

    The new `force_transition` tool lets an Admin MCP key recover an item with a reason and audit trail, using the same guarantees as REST. The ordinary `transition_item` tool gains no shortcuts.

  • Feature

    Extension ready from Settings

    From Settings you can download the extension ZIP already configured for your installation. Version, origin, manifest, and ID are verified by the backend; the release build rejects unsigned or inconsistent bundles.