Choose your Cleetus

Cleetus brings the same roles, teams and development workflow to three surfaces. Choose the one you need; each has its own installation and release channel.

If you already use VS Code, the independent extension keeps Cleetus in that editor. Its VSIX and the IDE installer have separate versions and update paths.

#A Mac development workspace

Choose the IDE for the full editor, Agent Command, team topology, tasks, review and Cleetus Design. Download its signed installer from the official public releases repository, verify the checksum and follow the installation guide.

The current IDE installer targets Apple Silicon. The CLI's Linux support does not mean the graphical IDE is a Linux product. Review platform requirements for native previews such as iOS and watchOS Simulator in the preview adapter guide.

#A companion for your iPhone

The iPhone app connects to your development host; it does not move the IDE or its provider credentials onto your phone. Internal TestFlight access is invitation only. Requesting access does not install a build or automatically enroll you.

Set up your iPhone, sign in to your Cleetus account if you use saved computer settings, then explicitly pair with the host. Account directory entries and discovery are hints; they cannot replace pairing, certificate checks or an approval. The host continues doing the work when the phone disconnects.

#A terminal or Linux headless host

The CLI uses the same Cleetus Core and role/team definitions. Its public download is a Node.js 22+ package, not a standalone Linux binary. Use only a published cli-v release with its matching manifest and checksums; documentation or a candidate's release notes alone do not establish a published download.

For an interactive Linux desktop, the CLI can use an already unlocked Secret Service and an explicit user service. For a server without that session, use the optional encrypted headless system service. That setup requires systemd, Python 3 and the listed official keyring tools. Installation is a deliberate administrator action; the host runs as your non-root account. It does not sign in coding agents or download models.

The terminal menus can browse managed role prompts, configure every member of a prebuilt team and open a team chat room. The catalog remains a draft reference until the host validates the exact selected configuration and you review the requested action. Follow the CLI walkthrough.

#One account, explicit permissions

Cleetus account sign-in manages your profile, saved nonsecret preferences and verified membership. Coding agents keep their own authentication and usage limits. Phone pairing and LAN collaboration have separate trust and consent.

Sign in through the account flow, review your chosen role's prompt/model/effort, and authorize actions on the host or through an explicitly scoped paired phone. A membership label, saved computer or model list is never execution authority.