Requirements & detection

C3 Desktop 0.1.3 is published as:

Linux x64 and ARM64 AppImages
macOS Intel and Apple Silicon DMGs/ZIPs
Windows x64 installer and ZIP

All current packages are unsigned launch betas. The packaged application lifecycle is exercised on all five targets. Linux remains the fully exercised C3 Bridge host path; macOS and Windows Bridge service execution and Windows snapshot-terminal behavior remain platform qualification gates.

Tools on the machine

C3 Desktop reports, rather than guesses, whether it can find:

Component	Why it matters
`c3sync`	Creates and administers the shared hub
`c3bridge`	Connects this machine's Herdr sessions to the control plane
Herdr	Hosts the workspaces, panes, terminals, and coding agents
Git	Supports the surrounding development workflow

It also checks for an initialized hub bundle, an enrolled C3Sync device, configured bridge state, active Herdr control sockets, and the platform/architecture.

Runtime installation

The desktop package includes the C3 renderer, hardened Electron main process, SSH support, and terminal runtime. It does not embed Herdr, c3sync, c3bridge, or a coding-agent CLI.

When a setup role requires C3Sync or C3 Bridge, the readiness screen can fetch the newest compatible public artifact for the current platform and architecture, verify its published SHA-256 digest, and place it in the app-managed runtime directory. The app shows unavailable or failed verification states instead of falling back to an unverified binary.

IMPORTANT — > Herdr is a separate project. Review its AGPL/commercial licensing before distributing it with any environment you manage.

Network paths

Local setup runs the installed CLIs directly on this machine.
Remote hub setup connects over SSH after showing the server's host-key fingerprint for confirmation.
Client control traffic connects from the Electron main process to the hub and uses the same pinned, end-to-end encrypted control protocol as C3 Mobile.

Next: guided setup.