How to Use OpenCode from Your Phone

The reliable architecture is simple: OpenCode runs on the machine that owns your project, while your phone acts as a remote control. Do not move the repository, model credentials, build tools, and complete development environment onto the phone unless on-device development is your explicit goal.

Recommended architecture

Mobile phone
  → private VPN or authenticated HTTPS route
  → OpenCode server on your computer
  → project files, tools, providers, and sessions

This keeps execution close to the real workspace while making approvals and follow-up work available away from the desk.

Set it up

1. Download OpenCode Mobile.
2. Set a password and start OpenCode 2’s shared service: opencode service set password '…', opencode service start, then opencode service status.
3. Choose Tailscale, Cloudflare Tunnel, local QR, Cloud Link, or another remote-access method.
4. Create a one-time login with opencode pair, or test the server’s /global/health endpoint for a manual connection.
5. Scan the pairing QR code, or add the full API base URL and password manually.
6. Select the project and confirm the expected session before sending work.

A standalone opencode serve process works too, but pairing requires the shared service, so use manual connection details.

You can save multiple servers and switch between them in Settings → Connection. The app keeps each server’s projects, remembered sessions, favorites, and notification records separate.

Good mobile workflows

• Check whether a long task is still progressing.
• Answer a permission or product question.
• Review Turn, Uncommitted, or Branch changes before accepting completion.
• Send a short follow-up, steer a running turn, or dictate it with voice input.
• Inspect a specific file, save a focused edit, or run a test command in the project terminal.
• Share a screenshot, document, or link from another app into a chat on Android.
• Switch or archive sessions while keeping each thread focused.

Use the desktop when a change requires broad code navigation, prolonged terminal interaction, complex conflict resolution, or detailed visual review.

Security boundaries

Your phone can become a route to source code and terminal access. Use strong server authentication, keep public exposure minimal, review permission prompts deliberately, and rotate credentials if a device is lost. Read the remote-access security guide before treating the setup as production-ready.

Continue with the mobile app setup guide, compare OpenCode Mobile with OpenCode Web, or diagnose a failure with the connection checklist.