v0.83.7
August 20, 2026
MCP profiles with tailored permissions, duplicate-free events. Each integration can have its own profile with a dedicated address and explicit permissions, OAuth authorization respects the profile's boundaries, and event delivery is protected from duplicates even when things go wrong.
-
Feature
MCP profiles with dedicated addresses
Each administrative MCP key becomes a profile with its own address: the connected client operates with exactly the profile's role, tools, and processes — ideal for giving each assistant or integration only what it needs. The management dialogs have been redesigned: clearer, mobile-friendly, and accessible.
-
Security
OAuth authorization within the profile's boundary
OAuth authorization started on a profile stays bound to that profile: role and permissions can only narrow, never widen. Guided connection works with the most common remote connectors, including claude.ai and ChatGPT.
-
Security
Explicit permissions for MCP keys
Key permissions move to an explicit model: "all tools" or "all processes" is a declared choice, not the side effect of an empty list. Existing keys keep their behavior; new ones start with the minimum needed.
-
Improvement
Duplicate-free events, even after a hiccup
Event delivery is now protected at the database level: re-entering the same phase does not create duplicate subscriptions, and an interruption mid-delivery neither applies an event twice nor loses it. Historical duplicates were automatically disarmed.
-
Security
Public links revoked with the process
When a process is deleted, its public share links are revoked: a previously issued link no longer shows the deleted process's content.