AI Integrator Mobile
Use Chat on a phone and, when enabled on the desktop, supervise a local Code run through a paired device.
Chat on a phone
The phone browser can open AI Integrator Chat with the same account used on the web. Chats, projects, agents, memory, Files, and model access follow the Chat account; the narrow layout changes the presentation rather than the account boundary. The public Downloads page currently provides the web Chat link and desktop installers and does not provide an App Store download link. Distribution status belongs to that page.
Enable Mobile Gateway
Remote Code control is a separate local connection. In the desktop application, the phone control beside Settings opens Mobile Gateway. The desktop enables Enable Mobile Gateway, selects a reachable private connection, and then selects Show pairing QR. Available routes can include a local network, ZeroTier, or Tailscale when each route is configured and available. The phone scans the short-lived code, and the desktop confirms the pending device before access is granted.
Authority and scopes
The desktop remains authoritative for projects, tasks, runtimes, vendor credentials, repositories, Git writes, and external actions. A paired phone receives only approved task views and scopes, such as run status, approvals, agent controls, bounded file previews, Git review, browser viewing or control, and attachment upload. The phone does not receive a generic shell, credential, repository, or deployment authority.
Availability and recovery
The gateway is off until explicitly enabled. Remote access depends on the private route, an available desktop, compatible versions, and the phone's granted scopes. A device can be renamed, have scopes changed, or be revoked in Mobile Gateway; rotating a lost installation identity revokes every paired device. This is not Chat synchronization, a second Code runtime, or a hosted Code relay. See Remote access, Tasks, PC, and Privacy.