Cleetus for iPhone
Keep your crew within reach: follow agents, inspect tasks and review requests from a development host you trust. The host runs the coding agents; the phone is their companion and review surface.
Get the app
Request internal TestFlight access. Access is invitation only. After an invitation arrives, install the assigned Cleetus build through Apple's TestFlight app and open it. There is no public App Store download or automatic enrollment promised by this request form.
Use a compatible current host build. App and host versions can expose different capabilities; an unavailable action stays unavailable rather than silently substituting a default agent, model or permission.
Prepare your host
On an Apple Silicon Mac, install Cleetus IDE. On a supported Linux host, install the CLI and prepare its secure credential store. A server without a desktop keyring can use the optional encrypted headless service.
Install your chosen coding agents or local model server separately. Cleetus account sign-in does not supply their credentials, subscriptions or models. An engine reported by your account is advisory until the current host confirms its available capabilities.
Sign in, then pair
- Sign in to Cleetus in the app. Using the same account as your host lets the app read your saved computer directory and reported engines. Those records do not establish a trusted connection by themselves.
- Put the phone and host on a reachable private network. This pairing path does not create an internet relay or change firewall rules.
- Enable Phone control on the host, review its private interface and port, and choose Show pairing invitation. The CLI provides the same controls from its attached terminal menu.
- In the app, choose the connection action and scan the host's invitation. Compare the eight-digit code on both devices, then approve it on the host and confirm it on the phone. Reject any unexpected request.
- Check that the app reports the host connected before starting or reviewing work. A remembered device, discovery result or notification does not prove that it is currently online.
The paired TLS fingerprint protects the host's identity even if its IP address is later reused by another computer. If the fingerprint changes, review the identity on the host; do not disable verification to force a connection.
Review and communicate
Available actions come from the connected host. You can inspect agent and team state, view supported conversations and request actions that the host explicitly advertises. Newer builds can browse shared role/team definitions and team chat; these require a compatible host and the applicable scoped approvals.
Review the complete prompt, selected engine/model/effort, project and action before allowing it. A phone decision applies to that immutable request only. Native provider sign-in, workspace trust and unsupported native consent stay with the provider's own interface. If there is no authorized review surface, new protected actions deny.
Reconnect and alerts
Keep the app's accepted pairing and the host's secure identity. Compatible builds can renew an expired short-lived session without pairing again. A changed fingerprint, revoked pairing or unavailable host requires review. See Phone control recovery.
Enable notifications in the app and allow iOS permission if you want alerts. Closed-app delivery also needs the separately reviewed host binding. Generic alerts and opted-in reply hints are wakeups, not action approvals or proof of immediate delivery; opening the app fetches current state. Network availability, iOS scheduling and notification settings can delay them.
For detailed trust, interruption and revocation behavior, read Phone control and Cleetus accounts.