Skip to content

OpenCode Mobile User Manual

This manual is the navigation hub for operating OpenCode Mobile after installation. It deliberately avoids repeating every control documented in the focused guides. If the app is not connected yet, start with Set Up OpenCode Mobile.

Area What it is for
Chat Start and follow tasks, review changes, answer approvals, use voice, choose models, and check usage
Projects Choose a project or worktree, browse and edit files, preview media, and manage entries
Terminal Open and use project PTYs
Settings Search and manage appearance, chat, voice, notifications, language, connections, providers, extensions, approvals, diagnostics, and updates

The chat library opens from the title at the top of Chat. A change chip above the composer opens the changes review overlay; the old Session and Files Changed tabs are gone.

Confirm three pieces of context:

  1. Connection: Settings shows the expected OpenCode server.
  2. Project: Projects shows the repository that should receive the task.
  3. Session: Chat shows the intended work thread.

This prevents the most expensive mobile mistake: sending a valid instruction to the wrong project or session.

  • Start and monitor tasks — choose a model, send a prompt, attach files, use commands or mentions, steer a running turn, and stop a bad direction.
  • Chats and sessions — search, favorite, rename, delete, fork, revert, and switch sessions.
  • Approvals and changes — answer permissions and questions and review diffs.
  • Voice — dictate one prompt or use the wake-word conversation loop.
  • Session usage — interpret context pressure, tokens, steps, and cost.
  • Notifications — completion and needs-input alerts.
  • Projects — select, add, archive, and switch projects; understand server-archived projects and worktrees.
  • Project files — search, read, preview, download, move, and save files.
  • Terminal — use the xterm-based project terminal and keyboard accessory.
  • Worktrees — create, select, and remove isolated working directories.

Choose a route from the remote-access overview. Use the dedicated Tailscale, Cloudflare Tunnel, local network, reverse proxy, or SSH forwarding guide when applicable.

Read the remote-access security guide before exposing a server. If the app returns HTML, 404, authentication errors, certificate errors, missing projects, stale realtime state, or terminal failures, work through the troubleshooting checklist.