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 diffs, answer approvals, use voice, and check usage
Projects Choose a project, browse and edit files, and manage worktrees
Terminal Open and use project PTYs
Settings Connections, providers, Cloud Link, notifications, voice, MCP, diagnostics, language, appearance, and updates

The Chats library opens from the title at the top of Chat. The session area and Files Changed are tabs inside the active chat.

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, steer a running turn, follow progress, and stop a bad direction.
  • Chats and sessions — search, favorite, archive, restore, fork, revert, share, and switch sessions.
  • Approvals and changes — answer permissions and questions and review diffs.
  • Voice — dictate one prompt or use conversation mode.
  • Session usage — interpret context pressure, tokens, steps, and cost.
  • Notifications — completion and needs-input alerts.
  • Projects — select, add, and switch projects; understand per-project sessions.
  • Project files — search, read, and save focused text edits.
  • Terminal — use the xterm-based project terminal and keyboard accessory.
  • Worktrees — create and manage 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, missing projects, stale realtime state, or terminal failures, work through the troubleshooting checklist.