Back to the changelog

v0.83.5

August 19, 2026

OAuth-ready MCP connectors, more transparent events. Remote connectors can authorize without keys in URLs, versioning preserves event actions, and telemetry now distinguishes receiving an event from actually applying an effect.

  • Integration

    OAuth for remote MCP connectors

    ChatGPT, claude.ai, and other compatible clients can connect through a consent- and PKCE-based OAuth flow. Authorized connections are visible and revocable from Profile; static keys remain available for clients that support headers.

  • Improvement

    Versions that preserve event actions

    Saving, duplicating, or creating a new version preserves event-linked actions and correctly remaps their destinations. An unsupported change is reported, never silently removed.

  • Improvement

    Event outcomes based on real effects

    History distinguishes receiving an event from making a transition. Delivery is reported as successful only when it actually produces a transition, update, notification, or another action; a subscription with no effect is shown as such.

  • Security

    Consistent Process Map scope and idempotent requests

    Process Maps accessed through MCP follow the same flow visibility as the interface. An idempotency key can no longer be reused with a different payload: the conflict is explicit and cannot hide a different request.

  • Improvement

    More predictable imports and lists

    Import, Designer, and versioning now share more consistent rules for null values, KPIs, transitions, and dedicated properties. Lists reject ambiguous filters or pagination, and the Task calendar indicates when it is showing a truncated set.