Encrypted in transit
HTTPS/WSS protects traffic between the App, Gateway, and Host.
Support
Fast answers. Clear security boundaries.
From Environment pairing and Runtime checks to safe API-key handling, these are the shortest paths for the current test build.
Credential protection
API keys land only on the selected Host—not in a Gateway database.
The App sends new connection configuration to your Host over an authenticated HTTPS/WSS connection. Server stores sensitive values in its Host-local secret store and redacts them from settings returned to clients. The account Gateway must not persist or log plaintext API keys.
Read the full security modelHost-local storage
Credentials remain in the selected Environment and are never returned in plaintext.
Short-lived pairing
A one-time Pair Token authorizes a device; it is not a permanent Environment credential.
Current E2EE boundary
The test architecture does not yet provide application-layer end-to-end encryption. Gateway terminates TLS and participates in forwarding, so connect only through a Gateway you trust.
Install FT2
Download and install the Android test build.
View steps →02Connect an Environment
Pair your Mac or Linux host by QR code or manual entry.
Troubleshoot connection →03Contact support
Include the version, Environment type, and a redacted error message.
[email protected] / [email protected] ↗Install the Android test build
Download the APK and allow your browser or file manager to install an app from this source. The current build supports arm64-v8a only.
Prepare an Environment
Start FT2 Server on your Mac or Linux host. Service credentials, projects, and agent history remain on that host.
Generate a one-time pairing code
Generate a short-lived Pair Token on the Host and scan it in FT2. The token only authorizes a new device; it is not the permanent identity of an Environment.
Check the Runtime Profile
In Environment settings, confirm that Codex or Claude CLI is detected, enabled, and authenticated on the Host.
Troubleshooting
Common issues
The Environment appears offline
First confirm the Host service is still running and can reach public HTTPS/WSS. Restarting Server does not require pairing again; do not delete the Host state directory.
The agent is installed but will not start
Installed does not mean authenticated. Confirm that the CLI runs independently on the Host and check its Binary, Home, Base URL, and authentication state in Runtime Profile.
A task has not changed for a long time
Open another page and return to the task to refresh, then confirm that the Environment is online. When contacting support, include the time, Environment type, and task title, but never a token or API key.
Is FT2 end-to-end encrypted?
Not at the application layer in the current test build. HTTPS/WSS encrypts transport, but Gateway is a TLS endpoint. Use a trusted Gateway and avoid highly sensitive workloads until application-layer E2EE is available.
What happens when I enter an API key in the App?
It travels over the authenticated TLS/WSS connection to the selected Host. Server keeps it in a Host-local secret store and returns only a redacted value. Gateway must not persist or log the plaintext key.
How should I report an issue safely?
You may share the app version, phone OS, Environment platform, and redacted errors. Remove project code, access tokens, Pair Tokens, API keys, and personal file contents.