Skip to main content
The Pioneer mobile app connects to existing gateways from iOS or Android. Use it to continue threads, check task output, switch workspaces, or steer a gateway away from the desktop app. The mobile app does not run the assistant by itself. The gateway owns workspaces, threads, model calls, tools, MCP servers, skills, tasks, artifacts, settings, and durable storage.

​
What it can do

The current mobile client includes:

​
Saved gateways and tokens

Mobile keeps a local list of saved gateways and stores gateway tokens separately in the platform secure store. That means the visible gateway entry can be edited or removed without showing the raw token back in the UI. If a token is rotated on the gateway, update the saved mobile connection with the new token.

​
Remote gateway first

The mobile app currently manages remote gateway entries. It does not install, start, or supervise a local gateway process on the phone. For mobile use, run a gateway on a computer, workstation, server, or other reachable host. Then add it in the mobile app with its address and bearer token.
Tool calls, local paths, MCP servers, provider requests, and task execution happen on the gateway, not on the phone. Permission modes and sandbox/resource policy are enforced by that gateway.

​
Consistency with desktop

Desktop and mobile use the same product concepts. A gateway, workspace, thread, provider, skill, MCP server, task, and artifact mean the same thing in both clients. The difference is responsibility: desktop can install, start, and manage a local gateway, while mobile connects to gateways that already exist.

​
Builds and locales

The mobile app targets iOS and Android and uses the same eight UI locales as desktop: English, German, Spanish, French, Hindi, Japanese, Russian, and Chinese.