Installing the command line tool got far simpler, Windows included

Summary

Setting up the Effigate CLI on a new machine used to require developer tooling most teams don't want to maintain just to run a small command-line helper. It now installs as a ready-to-run download, and Windows machines — previously unsupported — now work properly too.

What You Gain

Before this change, every machine you wanted to set up needed a working developer toolchain installed, just to get one small CLI running — overhead that had nothing to do with the actual work you wanted to do. On Windows, there was no supported install path at all, so teams running Windows machines simply couldn't use the CLI.

Now setup is a single download with a built-in verification step, and the only requirement on the target machine is a standard, widely available runtime (Node.js 20 or newer). Re-running the installer upgrades it in place. Windows now has its own proper installer, and a mismatch that used to make the CLI invisible to coding agents on Windows — even when correctly installed — is fixed, so agents running on Windows can use it exactly as they can on Mac or Linux. This closes the loop on the Windows agent fix from earlier this month: that fix got stuck runs moving again, and this one makes sure Windows never has that problem on a fresh install.

How It Works

• The CLI installs from a verified, ready-to-run download — no separate build step or developer tooling needed.
• Windows now has a dedicated installer, alongside the existing one for Mac and Linux, both documented in the Desktop App / CLI guide.
• A Windows-specific compatibility issue that could make a correctly installed CLI appear missing to an agent is resolved.

Where to Find It

Reinstall using the latest installer from the Desktop App / CLI guide inside your account — existing installs can upgrade in place by re-running it.

See what else shipped this month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.