Skip to content
← Back to Docs

Client Mode

Client mode lets your mobile app connect to the CLI daemon running on your desktop. View and interact with your AI coding sessions from anywhere.

What is Client Mode?

In client mode, MobileCLI:

  • Connects to a host machine via WebSocket
  • Receives real-time session updates
  • Sends input and receives output from CLI sessions
  • Works with the iOS app today. Android compatibility is validated through internal builds before public Android distribution.

Connection Methods

QR Code Scanning

The easiest way to connect. On your host machine, run mobilecli pair to display a QR code. On your mobile device, tap "Scan QR Code" and point your camera at the code.

The QR code contains the connection URL, device metadata, credential id, server id, and a one-time pairing token. The app stores the token securely and authenticates before the daemon sends sessions or terminal data.

Manual Configuration

When QR scanning isn't available, run mobilecli pair on the host and enter the full auth-v2 pairing details manually in Settings.

Host URL: ws://192.168.1.100:9847
Credential ID: [shown by mobilecli pair]
Server ID: [shown by mobilecli pair]
Pairing token: [shown by mobilecli pair]

Mobile App Features

The mobile client provides a streamlined interface optimized for phone and tablet use:

Session List

View all active and recent sessions from your host machine.

Real-Time Sync

Watch your AI's responses stream in real-time as they're generated.

Quick Input

Send messages and approve tool use from your mobile keyboard.

Notifications

Get notified when your AI needs input or approval.

Desktop Client Mode

You can also run MobileCLI in client mode on a secondary desktop. This is useful for:

  • Monitoring sessions on a second monitor
  • Accessing your development machine from a laptop
  • Team collaboration on shared sessions

Remote Access with Tailscale

Connect From Anywhere

For remote access outside your local network, install Tailscale on both devices. Tailscale keeps the daemon reachable only to devices in your Tailnet instead of exposing it through a public tunnel.