[FEATURE]: Mobile App

Feature hasn't been suggested before.

I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Currently, users wanting to access their OpenCode instance from a mobile device must rely on the mobile browser. While functional, the browser experience has limitations:

Suboptimal UX: Lack of native gestures, smooth transitions, and mobile-optimized input handling.
No Native Integration: Cannot leverage device capabilities like secure storage for API keys or push notifications for long-running task completion.
Connection Management: Manually typing IPs and managing connection state in a browser tab is less reliable than a dedicated app config.

Proposed Approach
Officially create the packages/mobile directory for a React Native app built with Expo. This app currently acts as a remote desktop client for the local OpenCode server.

Key Features Implemented:

Architecture: Expo SDK 54 with Expo Router for file-based routing.
Connectivity: Connects to opencode serve via local IP (with SSE support for real-time streaming).
UI: dedicated Chat interface with terminal styling, session management, and server configuration settings.

Why it belongs in OpenCode
Premium Experience: A native app provides the "wowed at first glance" design quality we aim for, with superior performance and responsiveness compared to a web view.
Market Gap: There is currently no true "vibe-coding" mobile experience offered by other AI development tools. A native mobile app would uniquely position OpenCode as the first to enable a seamless, high-quality coding workflow on the go.

This issue might be a duplicate of existing issues. Please check:

[FEATURE]: Mobile-friendly web UI #5126: [FEATURE]: Mobile-friendly web UI - This discusses improving mobile experience through web UI enhancements, while your proposal takes a different approach with a native React Native/Expo app

Feel free to ignore if your native app approach addresses different aspects or requirements than what's covered in #5126.

We will have a react native mobile app its on the roadmap

@adamdotdevin

Hi @adamdotdevin and @rekram1-node,
I have experience in React Native and am an avid user of opencode and would love working on this!

If anyone is interested, I started work on an app here https://github.com/georgi/opencode-mobile

I think making the web ui mobile friendly and less buggy should be first priority (#7530 et al). And installable as PWA.

@einarpersson

@einarpersson Take a look at shuvcode - it was many mobile improvements and the PWA thing already implemented. I also submitted it as a PR to opencode IIRC

Please consider shipping an analogue of the Remote Control feature of Claude Code in the mobile app once its development starts:
https://code.claude.com/docs/en/remote-control

Crucial aspect of this feature: it controls a running instance of the coding agent on your laptop, it is different from running a cloud agent off one's phone.

(I think a good avenue would also be making the web mode run as a PWA, but a native app could add features like notifications with actions buttons which I don't think Web Push supports.)

I built an open-source mobile client for OpenCode that I'm running in production:
https://github.com/mittaus/opencode-mobile-client

It consists of two parts:

Android app (Kotlin Multiplatform + Jetpack Compose) — real-time chat, sessions, git diffs, todos, permission prompts, token stats
Go gateway — sits between the app and opencode serve, handles API key auth, SSE fan-out to multiple clients, auto-reconnect, and
multi-project support (one opencode serve process per project directory, routed via X-Project-Path header)

The gateway auto-discovers project subdirectories on startup and launches a dedicated opencode process for each one, so you can
switch between projects from the phone without touching the server.

Happy to answer questions or collaborate if anyone is working on something similar.

Real-world experience with a third-party Android client

I just set up mobile control for OpenCode using opencode-remote-android (community project, v1.1.1). Here's what worked and where a first-party solution would be significantly better:

What worked

Server setup: opencode serve --hostname 0.0.0.0 --port 4096 with OPENCODE_SERVER_PASSWORD for auth — simple, no extra dependencies
Connection: The Android app (React + Capacitor) connects over LAN via the OpenCode HTTP API (/global/health, /session/*, /command)
Core features: Session monitoring, sending prompts, slash commands, and aborting tasks all work from the phone

Pain points that an official app would solve

No zero-config discovery — I had to manually type the LAN IP (192.168.x.x), port, username, and password. mDNS or QR-code pairing would eliminate this entirely
No remote access outside LAN — The app only works on the same WiFi. WebRTC or a tunnel would let me check sessions from anywhere
Auth friction — Basic Auth works but isn't ideal for mobile. Session-scoped tokens or ephemeral pairing codes would be much cleaner
Missing features — No push notifications when a long-running task completes, no voice input, no file attachment support

Why this belongs in core

The community built this because the need is real — the Android repo already has 60+ stars and the Telegram/Discord bot alternatives have 300+ and 100+ stars respectively. But these are all third-party workarounds. A first-party mobile experience (even just the pairing protocol + a reference app) would unify the ecosystem and ensure it stays compatible as the API evolves.

The architecture is already there (opencode serve exposes everything needed). What's missing is the discovery + pairing layer — exactly what this issue proposes.

scenario: you wire up an Expo client to a local opencode server over your home wifi, sessions streaming fine via SSE, then you walk out the door and the whole thing falls over. the part that breaks down isn't the UI or the SSE channel, it's connection state. mDNS discovery doesn't survive cell handoff, the IP you typed in settings is now wrong, and reconnect logic has to distinguish 'server died' from 'i changed networks' from 'phone slept and woke up'. the chat surface is the easy 20%. the boring 80% is a connection manager that handles tailscale-style reachability, token refresh on resume, and SSE backoff that doesn't drain battery. worth scoping that explicitly before the React Native work, otherwise it ships and feels broken on LTE.

Not quite what was asked, but we've been building Sesori for the past few months, native iOS and Android client specifically tailored for OpenCode. Posting in case it's useful for anyone landing here who would like mobile today. Sesori is:

E2E encrypted, running on your machine
Open source
OAuth device pairing (GitHub/Google/Apple), so adding a new phone or laptop doesn't require touching the host after setup
Not just a terminal wrapper

Some relevant links:

Website: https://sesori.com/
Repo: https://github.com/sesori-ai/sesori_apps_monorepo
Quickstart: https://docs.sesori.com/get-started/quickstart

We'd be thrilled to get some feedback 🙏

https://sesori.com/

This is actually good, need improvements to UIUX and speed of the relay.

For folks looking for a native mobile app for OpenCode, check Paseo: https://github.com/getpaseo/paseo/

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

I built an open-source Expo client for the OpenCode V2 HTTP API that utilizes the /pair authentication and Tailscale. If anyone wants to test or contribute, here is the repo https://github.com/omnicus/opencode2-mobile

https://sesori.com/

This is actually good, need improvements to UIUX and speed of the relay.

Thanks. We've improved a lot since then too! UI and UX is much smoother!!

Also, we now support many harnesses (OpenCode, Claude Code, Codex, Pi, OMP, Hermess, Cursor) + about to launch: GitHub Copilot, DeepSeek and Grok Build

Navigation Menu

Repository navigation

[FEATURE]: Mobile App #6536

Feature hasn't been suggested before.

Describe the enhancement you want to request

Real-world experience with a third-party Android client

What worked

Pain points that an official app would solve

Why this belongs in core

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[FEATURE]: Mobile App #6536

Description

Feature hasn't been suggested before.

Describe the enhancement you want to request

Activity

github-actions commented on Dec 31, 2025

rekram1-node commented on Dec 31, 2025

ronak-guliani commented on Dec 31, 2025

georgi commented on Jan 20, 2026

einarpersson commented on Feb 16, 2026

gergesh commented on Feb 20, 2026

TomasHubelbauer commented on Feb 25, 2026

mittaus commented on Mar 14, 2026

Strelitzia-reginae commented on Apr 3, 2026

Real-world experience with a third-party Android client

What worked

Pain points that an official app would solve

Why this belongs in core

m13v commented on Apr 28, 2026

AlexDochioiu commented on May 20, 2026

chandralegend commented on May 23, 2026

boudra commented on May 24, 2026

github-actions commented on Jul 24, 2026

eivindjonassen commented on Aug 28, 2026

AlexDochioiu commented on Aug 28, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions