FLAME DOCUMENTATIONAvailable soon

Flame Mobile

A native iOS and Android companion for your Flame workstation. Follow agents, review changes, manage todos, and reach your terminal from your phone. Available soon.

Product overview ↗
Available soon

This guide introduces the companion workflow ahead of availability. Public iOS and Android download links will be added to the Flame Mobile page when available.

Availability

Flame Mobile for iOS and Android will be available soon.

  1. Use this guide to get familiar with pairing and the connected workflow ahead of availability.
  2. Keep Flame IDE updated so the desktop and companion can negotiate supported features when you connect.
  3. Follow product updates through the mailing list for news about availability.

Pair with Flame IDE

When you have access to the native app, pairing starts at the development computer.

  1. Open Remote Access in Flame Desktop and choose Secured Access. New installations default to Off.
  2. Generate a pairing QR code and scan it inside Flame Mobile.
  3. Enter the two-digit confirmation number shown on your phone into the desktop. Scanning alone does not grant access.
  4. Choose the device's access duration. Review and revoke paired devices from the desktop when needed.

Pick up the next useful task

The companion operates against your connected development computer.

  1. Choose a project to browse files, inspect changes, or open an AI conversation.
  2. Review agent tool requests before approving or denying them. Host permissions and supported runtime controls still apply.
  3. Use Git diffs, history, search, tests, and scripts to follow the work without recreating your environment on the phone.
  4. Use the TO DO page for the same global and project todos as the desktop, including details, completion, reminder dates, and prepared AI chats.

Understand the connection

Your workstation hosts the repository, commands, and running processes.

  1. Keep the development computer online with Flame running. Both endpoints connect outward to the relay, so pairing does not require a public desktop URL or an inbound mobile port.
  2. Workspace traffic is encrypted end to end. The relay handles ciphertext and connection metadata, including timing and traffic volume.
  3. Set Remote Access to Off to close relay connections, or revoke an individual device to end its access.

Related guides

Have a question or found a missing step?Send feedback