Skip to content
OC Remote

Guide

How to use OpenCode from your iPhone

Start the stable OpenCode V2 service, pair OC Remote over your LAN or Tailnet, and monitor or control sessions from iPhone and iPad.

OpenCode runs on a computer or server you control. OC Remote is the native iPhone and iPad client for that server: the repository and agent do not move to a second hosted service.

Stable OpenCode V2 is the primary integration. OC Remote also keeps a separate adapter for classic V1. OpenCode V2 itself is stable, but its HTTP API is still experimental, so future OpenCode releases can require an OC Remote update.

1. Start the stable V2 shared service

Start the service, print its current address, and create a one-time pairing link:

Stable OpenCode V2
opencode service start
opencode service status
opencode pair

The default shared-service port is 49374 on macOS, Linux, and WSL, and45278 on Windows. Treat opencode service status as the source of truth when your installation uses a different address.

2. Make the service reachable from the phone

If the phone and host share a trusted private network, use the host's private address. HTTPS is preferred because it encrypts credentials, prompts, attachments, and session data in transit. OC Remote permits direct HTTP only for loopback, private-network, link-local, and Tailscale addresses; it rejects cleartext public hosts.

Tailscale Serve is a convenient encrypted route. On a macOS, Linux, or WSL host using the default V2 port:

Stable V2 over Tailscale Serve
tailscale serve --bg 49374
opencode pair --url https://<machine>.<tailnet>.ts.net

3. Pair OC Remote

Install OC Remote, open Settings → Connection, and choose Pair with OpenCode. Scan the QR code or paste the pairing link. Current pairing links work once and expire after five minutes.

OC Remote redeems the code for a session token and validates that token against an authenticated API route before saving the connection. Saved passwords and pairing tokens are kept in the iOS Keychain.

4. Connect a classic V1 server manually

A dedicated opencode serve process remains supported for classic setups. Use the address and port your server actually reports; 4096 is the common example:

Classic server example
export OPENCODE_SERVER_PASSWORD="a-long-password"
opencode serve --hostname 0.0.0.0 --port 4096

In OC Remote, add the reachable server URL and credentials manually. Never expose a server publicly without authentication, and use HTTPS for any public route. See the secure connection guide for LAN, Tailscale, and TLS options.

5. Monitor for free, then control with Pro

Once connected, you can use the free monitoring loop:

  • Browse projects and sessions and see which runs need attention.
  • Follow live messages, tool calls, task lists, token usage, and agent results.
  • Browse files and inspect line-by-line session diffs.

OC Remote Pro adds the control surface:

  • Create sessions, send prompts, and choose server-defined agents and models.
  • Answer structured questions, approve permissions, and manage queued work.
  • Continue, retry, stop, fork, revert, or unrevert sessions.
  • Use interactive PTY terminals and manage providers and MCP authentication.
  • Dictate on device, even offline after the WhisperKit model download.

Eligible new subscribers can start with a 7-day free trial, then €5.99/year in the euro storefront; local pricing may vary. The annual subscription renews automatically until canceled in App Store account settings.

Install OC Remote

Monitor for free. Eligible new subscribers can start with a 7-day free trial, then €5.99/year in the euro storefront; local pricing may vary. Requires iOS or iPadOS 18.

Download on the App Store
Download on the App Store