From installation to your first result

This guide focuses on iOS / iPadOS and calls out Android differences. Check the selected release for its actual capabilities.

Choose an installation channel

Open the release centre and choose Floe Agent, Mac Bridge or iOS Bridge. GitHub iOS IPAs require your own signing. Apply on the website for TestFlight access; applying does not guarantee immediate eligibility. App Store availability is determined by the actual store listing.

On Android, download the signed APK for the selected public alpha. A complete current APK does not require installing every intermediate version. A delta needs its exact stated base. If Android reports a different signer, preserve your data rather than uninstalling just to proceed.

Complete an AI task

Prepare: a working provider configuration and API key. Choose an image-capable model when the task needs to read pictures. Your chosen provider handles cloud requests under its own pricing and data policies.

1. Add the provider, endpoint, key and model in settings. Confirm a simple text conversation works.
2. Create a task and select its workspace. Add a non-sensitive test file through the file picker.
3. Request a concrete result, for example: “Turn this material into a checklist and save it in this workspace.” Grant access to the relevant files and tools as needed.
4. Open the output and check its content, location and format. Close and reopen it to confirm it was saved.

If it fails: check the key and endpoint for authentication errors, use an image-capable model for images, and reselect the original workspace for file-access problems. A tool success message alone does not prove the result was saved correctly.

Run code on your device

Prepare: enough storage and memory. Current iOS uses a shared ARM64 Linux runtime while retaining task and project ownership. Packages must match the guest architecture.

1. Download and verify resources in execution-environment settings, then open the current workspace terminal.
2. Run pwd and uname -m to check the directory and actual architecture. Install Python, Node.js or other required packages for that environment.
3. Run a small program and open its output. For an HTTP service, choose Run as web service, wait for a real response, then preview it.
4. Stop the owning job or service when finished. Hiding the terminal or closing the preview does not stop background work.

If it fails: inspect installation, startup and job output first. On Android Alpha29, if the terminal stops starting after an upgrade, update runtime components separately under Settings → Execution → Local Environment. Preserve project files before repair; do not reset or delete data as a first step. See terminals and environments.

Create and save a 3D model

Prepare: an iOS/iPadOS release with the native 3D workbench. Imported meshes do not gain native parametric history, and supported operations vary by format.

1. Create a native 3D model through the creative workflow, beginning with simple geometry.
2. Refine dimensions, holes or fillets in the same model. When using the assistant, identify the current model and the intended change.
3. Check geometry, materials and views; save the .floecad file and reopen it.
4. Export an image or supported 3D format for the intended use, then check it in the receiving tool.

If it fails: preserve read-only imports rather than treating successful import as editable support. Undo a failed geometry change to a recoverable state. See the native 3D manual.

Choose the right Bridge

Mac Bridge: install a selected release, open the menu-bar app, and connect from Floe on the same Mac. Compare the code and approve both prompts. Check the directory and read a test file before starting work. Commands are not replayed after disconnection. If the menu-bar icon is missing, relaunch the app; if pairing fails, check both versions and confirmations.

iOS Bridge: start with the versioned installation instructions. Version 1.0 requires signing with Network Extension capabilities; arbitrary re-signing setups are not guaranteed. Complete preparation in the app and approve client pairing on the device. Access is local by default; enable LAN access only when needed. Read the screen after an action; do not automatically repeat a tap when its result is unconfirmed.

Save, recover and get help

Confirm saving in each Office, media or 3D editor. Save-as and export do not automatically replace the original. After Android external-editor or Linux edits, wait for writeback before reopening; preserve recovery copies when conflicts remain. Keep independent backups of important files.

For support, describe the version, device, steps, expected result and actual result in the support channel. Submit only necessary diagnostics or screenshots voluntarily; never include passwords, keys or private files. Continue with the full manual.