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 on Android.
Before sending work
Confirm three pieces of context:
- Connection: Settings shows the expected OpenCode server.
- Project: Workspace shows the repository that should receive the task.
- Session: Chat shows the intended work thread.
This prevents the most expensive mobile mistake: sending a valid instruction to the wrong project or session.
Chat and task control
Use Start and Monitor OpenCode Tasks to choose an agent and model, write a useful instruction, attach context, follow progress, stop a bad direction, and decide whether the result is complete.
Use Manage OpenCode Sessions to switch, rename, archive, restore, delete, share, fork, or revert work threads. Keep one outcome per session so context usage and review remain understandable.
Permissions, questions, and changes
OpenCode may need permission to use a tool or a product decision before continuing. Review Permissions and Code Changes explains temporary and persistent approval choices, question responses, changed-file inspection, and safe completion checks.
Treat permissions as security decisions. Read the requested action, active project, command, and path before approving.
Voice and notifications
Use Voice with OpenCode for a reviewed dictated prompt or the foreground conversation loop. Voice input does not remove the need to inspect high-impact instructions on screen.
OpenCode Task Notifications covers Android completion alerts, battery restrictions, app lifecycle limits, and the difference between a notification and authoritative server state.
Usage, models, and providers
Track Token and Session Usage explains context utilization, input and output tokens, reasoning tokens, caching, steps, and estimated cost.
Configure Providers and Models distinguishes OpenCode server credentials from AI-provider credentials and explains authentication, visible-model selection, and capability discovery.
Workspace files and worktrees
Edit Workspace Files is appropriate for searching, reading, and saving a small text correction with a conflict check. Use Chat or a desktop editor for multi-file work.
Manage OpenCode Worktrees covers the experimental worktree controls and the consequences of reset and removal operations.
Mobile terminal
Use the OpenCode Terminal from Android for focused, non-interactive commands such as tests, Git status, and short logs. It is a line-oriented project console, not a complete VT terminal emulator.
MCP and diagnostics
Troubleshoot MCP and Diagnostics explains server health, realtime fallback, MCP state, LSP state, and formatter availability. Optional endpoints vary by OpenCode version and deployment.
Remote access and connection failures
Choose a route from the remote-access overview. Use the dedicated Tailscale or Cloudflare Tunnel setup when applicable, and read the remote-access security guide before exposing a server.
If the app returns HTML, 404, authentication errors, missing workspaces, stale realtime state, or terminal failures, work through the connection troubleshooting checklist.