Local project directories now reach the right machine
A local project directory could go unused on machines running more than one connected daemon; it now always reaches the exact machine it was set up for.
Summary
A correctly configured local project directory could still go unused if you had more than one machine connected under the same account — agents would fall back to a fresh checkout instead, sometimes failing outright if the project's other resource needed access the fallback machine didn't have. It now always reaches the specific machine it was set up for.
What You Gain
If you run more than one connected machine — say, a Mac and a Windows machine both set up for the same account — this previously meant Effigate Command Center couldn't reliably tell which one actually held your local directory, and could pick the wrong one. Now the exact machine that claimed the task is the one that's used, every time, regardless of operating system.
Where to Find It
This fix applies automatically — no changes needed to your existing local directory setup.
See what else shipped this month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.