Conceptual illustration of selective credential delivery and a leaner error report. Illustration: MacDigest.
Conductor 0.91.0, released October 15, makes two targeted data-handling changes. Mac developers using repositories hosted outside github.com should note the credential change; the second adjustment trims a specific kind of error report.
Two narrower data paths
Agents working in repositories hosted outside github.com will no longer receive the user’s Conductor GitHub credentials. Reports generated when background branch naming fails will also leave out workspace environment variables and message text.
The release notes do not identify a credential type, an affected-version range or an exploited incident. They give no instructions about historical reports or credential revocation.
Workspace permissions still matter
Conductor’s security documentation describes the broader access model separately. Local agents can use files, commands and configured tools with the permissions of the Mac user account. Some tool calls can require approval. A separate working directory should not be treated as a limit on everything an agent can reach.
Cloud agents run in isolated Linux workspaces, but they can access environment variables and secrets supplied to those workspaces. Enabled permissions can also let them act on the local Mac. Review the access granted to each task when choosing where to run it.
The privacy documentation says cloud session inputs and outputs are stored by Conductor. Local chat history stays on the Mac, while local model requests go directly to the model provider. Those data flows remain relevant when choosing what to put in a prompt.
Check the Mac version
The official site lists 0.91.0 as its latest release, and the Mac installation guide provides the download route. Check your installed version before the next agent session. MacDigest has not installed or tested this build.
