Agent Workspaces

Conductor 0.87 Puts More Control Around Routine Triggers

By Kaleido Field Staff · September 20, 2026

Citation-ready: Conductor 0.87 adds label, author and base-branch filters for GitHub-triggered routines and stops shared cloud setup scripts from automatically executing on collaborators' Macs.

Evidence boundary: Vendor changelog and proposed verification criteria. Security fixes are vendor-reported; no exploit reproduced, collaborator machine accessed or software installed.

What happened and why it matters

The trigger identifies which event deserves work. The execution environment determines whose machine and resources perform it. Sharing a configuration should not blur those two decisions.

Primary evidence

Primary reference: Conductor version 0.87.0 changelog. Kaleido Field checked the event date and the article's attributed facts against this source.

The filter can be narrower than the repository

Routines can filter GitHub events by label, author and base branch, including exclusion rules, and use several triggers. The update also adds a weekdays schedule. These are selection controls; the changelog does not claim that they prove the task was completed correctly.

A useful check includes one event that should match and one that should not. Record which configuration was active for each result. This can expose a broad trigger before it produces unnecessary work or notifications.

Shared scripts need a visible destination

The release separates personal and shared cloud repository script settings and identifies whether a script is runnable in the cloud or local mirror. It also reports the change that prevents automatic shared setup-script execution on collaborators' Macs.

Before running a shared script, inspect its intended environment and effects. Afterward, distinguish a launched process, a completed task and a verified external result. Our tool-governance analysis explains why a configuration being available is not authorization for every action it can perform.

Evidence boundary

Vendor changelog and proposed verification criteria. Security fixes are vendor-reported; no exploit reproduced, collaborator machine accessed or software installed.