Mobile client for self-hosted AI coding agents and remote approvals
Experience OpenCode - AI from User Deep, a mobile companion that connects Android devices to a self-hosted OpenCode CLI server for remote session control. The app streams chat token-by-token and displays diffs so developers can monitor AI reasoning and review proposed code changes in real time. It supports multiple connection tunnels and biometric session locks, making it useful for engineers who need remote oversight of long-running automated coding tasks.
What does the app actually do for a self-hosting workflow?
The app acts as a thin client for an OpenCode CLI server, letting users monitor and steer AI coding sessions running on their own infrastructure. Moreover, it provides real-time streaming chat so you can follow model output token-by-token and an integrated file diff viewer to inspect proposed modifications before approving writes. This design keeps model calls and API keys confined to the host machine rather than the mobile device.
Does it affect device or server performance during remote sessions?
Remote monitoring runs as a lightweight client connecting to an existing OpenCode instance, so the mobile device primarily handles streaming and display tasks. In addition, the app supports multiple sessions for switching between tasks without reconnecting each time. The server handles compute-heavy model inference, meaning the phone’s CPU and RAM are used mainly for UI rendering and secure connection management.
Is it safe to approve changes from a phone?
Security features include biometric unlock to protect session access and a remote tool-call approval system for authorizing shell commands or file system actions. In practice, this means you can require explicit approval on the phone before the server executes potentially destructive operations, and all model calls and keys remain on your infrastructure according to the app’s privacy model.
Do I need technical knowledge to operate the client correctly?
Yes, the app requires a running OpenCode CLI instance installed via npm and familiarity with connecting devices through local networks or tunneling services such as Tailscale or Cloudflare Tunnel. For that reason, it targets developers who self-host agents; the workflows assume you can manage server setup and tunneling rather than offering a guided onboarding for non-technical users.
A practical mobile tool for self-hosting developers with one clear trade-off
OpenCode is a focused mobile control point for engineers who run their own OpenCode servers and need remote oversight of agent activity. It enforces a privacy-first architecture and supports secure approvals, but it depends on a separate self-hosted server and network tunneling to function, which limits use to developers comfortable managing that infrastructure.
