v0.93.8
October 4, 2026
Who did what is now visible in case history, even when automation is the one acting: an action taken through a connected assistant (MCP) now shows who asked for it and which assistant, not just "System"; starting a case through an external automation key shows the key's name, not the case's assignee; entering a phase because a queue slot freed up shows "WIP release" instead of attributing the action to whoever closed the previous case; a vendor administrator temporarily operating inside the organization for support shows "FlowSharp Support", not a technical code. Existing history rows stay as they are: the new labels apply from this release onward.
-
Improvement
Timeline: who did what, even when automation acts
Every row in a case's history now shows who acted, not just what changed. An automatic rule that fires right after a person's action shows "Automatic rule · on behalf of <name>"; entering a phase because a queue slot freed up shows "WIP release", attributed to the engine rather than to whoever closed the previous case; a scheduled start, a timeout or a published event each show a dedicated label; a sub-case created by a parent case shows "Sub-case". Rows written before this release keep the labels they already had.
-
Improvement
MCP assistants and API keys recognizable in the timeline
An action taken through a connected assistant (for example Claude via MCP) now shows the name of the person who asked for it together with the assistant used — for example "Mario via Claude" — instead of a generic "System" label. A start or an action coming from an external integration authenticated with a key now shows that key's name, no longer the case's assignee. A vendor administrator temporarily operating inside the organization for support shows "FlowSharp Support", never a name or a technical code.
-
Improvement
History via API and MCP with a structured actor
The history response for a case, both from the REST API and for assistants connected via MCP, now carries an author broken down into separate fields — person, assistant, key, engine — instead of a single text line. The new author field never contains an internal identifier for the person or the key: only a readable label.