A Repository Problem No Longer Looks Like a Clean Working Tree
Effigate Command Center now tells a real repository problem apart from a clean, ready-to-use one, instead of assuming every error means nothing to check.
Summary
Before running a task against a local project directory you manage yourself, Effigate Command Center checks that it has no unsaved changes and brings it up to date. That check could previously be fooled by an unrelated problem with the repository itself, letting an agent run against a folder that hadn't actually been verified safe. It now tells a genuine problem apart from a folder that's simply clean and ready.
What You Gain
Previously, if the safety check itself failed for a reason unrelated to your actual work — a permissions issue, a temporarily locked repository, or a repository that was simply too large to check in time — Effigate Command Center treated that failure the same way it treats a folder that isn't a repository at all: it skipped the check and let the task run anyway. That meant an agent could occasionally be let loose on a directory that was never actually confirmed to be safe, including one that might have held work you hadn't saved yet.
Now, a folder that genuinely isn't a project repository is still skipped exactly as before, and so is a clean one with nothing to update. Anything else stops the task and shows you the actual problem, so you can resolve it before any agent touches that folder.
How It Works
- A local directory that isn't a git repository is still skipped, exactly as before.
- A clean, up-to-date directory still runs normally.
- Any other repository problem now stops the task and shows the real error, instead of letting the task proceed.
Where to Find It
This applies to any project set up to run against a local directory. Update to the latest desktop app or standalone command-line tool to get this fix — it isn't a server-only change.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.