Feature Request: Mobile version of OpenCode (Android/iOS/Web UI) #10288

Activity

1. github-actions

   assigned

   adamdotdevin

   on Jan 23, 2026
2. github-actions

   added

   webRelates to opencode on web / desktopRelates to opencode on web / desktop

   on Jan 23, 2026
3. github-actions commented on Jan 23, 2026

   

   github-actionsBot

   on Jan 23, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • [FEATURE]: Mobile-friendly web UI #5126: [FEATURE]: Mobile-friendly web UI - Request for mobile-friendly web UI for on-the-go usage
   • [FEATURE]: Mobile App #6536: [FEATURE]: Mobile App - Comprehensive proposal for a React Native mobile app built with Expo
   • [FEATURE]: Is it possible to use opencode in browser ? #7917: [FEATURE]: Is it possible to use opencode in browser? - Browser-based access to OpenCode with GitHub repo connection
   • Poor mobile web experience. #7990: Poor mobile web experience - Bug report detailing multiple mobile web UX issues that need fixing

   Feel free to ignore if none of these address your specific case.
4. shawnyeager commented on Jan 25, 2026

   

   shawnyeager

   on Jan 25, 2026

   More actions

   +1 for PWA as a lightweight first step.

   Home server or laptop + OpenCode web w/ PWA as a systemd service = on-the-go success.

   👍React with 👍19Reacted by cruzanstx, Caleb Reyes, Antonio Mancini, Jad Tala, Christoph Klingspor, db, Dave Lasley, IceOnly, Maxim Crabbé, Martin Kunz and 9 more
5. InCerryGit commented on Feb 11, 2026

   

   InCerryGit

   on Feb 11, 2026

   More actions

   I am currently running OpenCode Web and then reverse proxying it to a VPS for use on mobile devices such as phones. PWA functionality is very much needed.

   👍React with 👍2Reacted by Michael De Rubertis and Simon-Martin Schröder
6. einarpersson commented on Feb 16, 2026

   

   einarpersson

   on Feb 16, 2026

   More actions

   I don't want a native mobile app, i just want the web ui to be mobile friendly

   👍React with 👍9Reacted by Michael De Rubertis, vipervire, Larry Reap, Rogers de Cristo, Jesper Ordrup, Javan Friedel, GoldenWarriorM, Esa-Matti Suuronen and dmdeemer
7. martynpekala commented on Mar 14, 2026

   

   martynpekala

   on Mar 14, 2026

   More actions

   @az0307 try my app and let me know what you think 😉
   https://github.com/martynpekala/openlens-qr

   👀React with 👀5Reacted by Hamzah Muhammad, Zai , Roi Mallo, Eduardo Fonseca and cz4u
8. alexandre-leng commented on Apr 14, 2026

   

   alexandre-leng

   on Apr 14, 2026

   Last edited by alexandre-leng

   More actions

   Can be great Android will be in next month a desktop os and Google want to ptomote
9. thdxr

   removed

   webRelates to opencode on web / desktopRelates to opencode on web / desktop

   on May 3, 2026
10. AlexDochioiu commented on May 15, 2026

    

    AlexDochioiu

    on May 15, 2026

    More actions

    Not affiliated with anomalyco, but we also wanted this so much we decided to make it happen and put the last 2-3 months on it. We just launched Sesori into open beta and we'd absolutely love some feedback! It's fully free, Open-Sourced and E2E Encrypted.

    That's a quick start for anyone wanting to take it for a spin: https://docs.sesori.com/get-started/quickstart

    ❤️React with ❤️1Reacted by Stan Vladut Angel
11. OpenCodeEngineer commented on May 17, 2026

    

    OpenCodeEngineer

    on May 17, 2026

    More actions

    Backbone decision update: we reviewed PR #10624 vs #1593 and selected #10624 as the baseline for Android.

    Execution plan now in progress:

    1. Add control.design.md describing user journeys, STT, notifications, and Tailscale usage.
    2. Rebase/import feat(mobile): add React Native mobile app for opencode #10624 mobile package into a working branch.
    3. Add reliability upgrades: reconnect/backoff, notification triggers (task complete + attention required), and Tailscale connection guidance.
    4. Produce Android APK and verify connection to a live server over Tailscale.

    We will post implementation status and APK build/test notes in follow-up comments.

    👍React with 👍3Reacted by Alexandre, Yuris Cakranegara and nsoderstromgmp
12. OpenCodeEngineer commented on May 17, 2026

    

    OpenCodeEngineer

    on May 17, 2026

    More actions

    Progress update on Android backbone branch ():

    • Added (user flows, STT, notifications, reconnect, Tailscale usage model).
    • Imported PR feat(mobile): add React Native mobile app for opencode #10624 mobile package as baseline.
    • Implemented reliability upgrades in mobile app:
      • SSE reconnect backoff + jitter + disconnect tracking
      • timeout controls for non-SSE HTTP calls
      • connection issue notification category with dedupe
      • improved Tailscale connection guidance in add-connection flow
    • Baseline checks:
      • in : pass
      • : warnings remain (peer deps + Expo dependency hygiene)

    Current blocker for local APK generation in this environment:

    • Android SDK/adb missing ( not set), so cannot build an APK locally.

    Next step: either provision Android SDK locally or use EAS cloud build to produce APK artifact, then verify connect/stream/notify behavior against a live OpenCode server over Tailscale.
13. OpenCodeEngineer commented on May 17, 2026

    

    OpenCodeEngineer

    on May 17, 2026

    More actions

    Implementation update for Android backbone ():

    Completed:

    • Added with user flows for Tailscale connectivity, STT, realtime updates, reconnect behavior, and attention/task-complete notifications.
    • Imported PR feat(mobile): add React Native mobile app for opencode #10624 mobile baseline into this branch.
    • Implemented reliability upgrades:
      • SSE reconnect with exponential backoff + jitter + disconnect tracking
      • prolonged disconnect notifications with dedupe controls
      • HTTP timeouts for non-SSE API calls
      • Tailscale connection guidance in add-connection UX
    • Validation:
      • (from ) passes
      • still reports dependency hygiene warnings
    • Built Android release APK locally:
      • Path:
      • SHA256:

    Remaining to close end-to-end objective:

    • Install APK on physical Android device.
    • Verify connect to live OpenCode server over Tailscale.
    • Verify realtime stream + permission/question alerts + task-complete notifications in that environment.

    I can drive that verification next once a reachable Tailscale server endpoint and Android device testing context are available.
14. OpenCodeEngineer commented on May 17, 2026

    

    OpenCodeEngineer

    on May 17, 2026

    More actions

    Android backbone progress update:

    • Selected PR 10624 as base and imported mobile package into branch feat/android-backbone-10288.
    • Added control.design.md and updated docs/android.md with architecture, constraints, and verification log.
    • Implemented reliability improvements:
      1. SSE reconnect with exponential backoff + jitter + disconnect tracking
      2. HTTP timeout handling for non-SSE calls
      3. Connection notification category with dedupe controls
      4. Tailscale connection guidance in add-connection UX
    • Validation:
      • mobile typecheck passes
      • expo-doctor still reports dependency hygiene warnings
    • Built Android release APK successfully:
      • packages/mobile/android/app/build/outputs/apk/release/app-release.apk
      • SHA256: 2e34212901fbec4cedcd2db1f678950b83b719ccfb34e63d43ba2372ebe6a134
    • Tailscale server smoke test passed using opencode serve on 0.0.0.0:4097 and health checks via localhost + tailnet IP.

    Remaining blocker to close full E2E:

    • No reachable Android test device/adb endpoint in this environment, so APK install + on-device stream/notification validation is pending until device access is available.

    🚀React with 🚀3Reacted by Simon-Martin Schröder, Ashutosh Sononey and isaacforde
15. boudra commented on May 24, 2026

    

    boudra

    on May 24, 2026

    More actions

    For folks looking for a native mobile app for OpenCode, check Paseo: https://paseo.sh/opencode
16. cmate0s commented on Jul 10, 2026

    

    cmate0s

    on Jul 10, 2026

    More actions

    Hi! I’ve built a lightweight solution that addresses exactly this feature request.

    It’s called opencode-remote: a wrapper and WebSocket bridge that mirrors your running local terminal session (1:1 mirror using Node.js IPC, not a separate process) to a mobile-optimized Progressive Web App (PWA) using xterm.js.

    This setup allows you to:

    • Monitor terminal output in real-time on your mobile device.
    • Send new tasks and accept/deny agent permissions remotely when away from your desk.
    • Keep the exact terminal state synchronized thanks to dynamic terminal resizing and alternate screen buffer restoration.
    • Set up a secure Cloudflare Tunnel automatically with a single command (no port forwarding required).

    You can find the repository, instructions, and architecture diagrams here: https://github.com/cmateos91/opencode-remote

    Hope this is helpful or inspires future native remote control designs!
17. alexandre-leng commented on Jul 10, 2026

    

    alexandre-leng

    on Jul 10, 2026

    More actions

    This project need to be maintain by opencode and integrate to opencode natively
18. linghengqian commented on Jul 11, 2026

    

    linghengqian

    on Jul 11, 2026

    More actions

    • It looks like OpenCode 2.x is close to completing this, given that the opencode pair bash command has already appeared. See https://x.com/thdxr/status/2075690050805739682?s=20 .

    we are playing with this. it's why we added opencode pair in v2

    👍React with 👍1Reacted by Carlos Mateos
19. star-Cosmo commented on Aug 22, 2026

    

    star-Cosmo

    on Aug 22, 2026

    Last edited by star-Cosmo

    More actions

    Hi, thanks for this feature request.

    Would it be technically feasible to link OpenCode sessions via WeChat for push notifications (e.g., task complete, attention required) and quick replies?

    Just like those traes, a WeChat ClawBot appears in WeChat.

    Would love to hear if this aligns with the mobile roadmap. Thanks!
20. pstayets commented on Aug 26, 2026

    

    pstayets

    on Aug 26, 2026

    More actions

    Not the native app this asks for, but a today-option. shell opencode on the box prints a link that opens the real OpenCode TUI in a phone browser, watch and type, which also covers the approve-a-permission-from-my-phone case in #39628 since typing into the link is enough. Disclosure, I work on Pilot Protocol, which develops shell.online. MIT, single binary, macOS and Linux. Caveats, a TUI in a phone browser is cramped next to a real mobile UI, and the link is a bearer credential, anyone holding it can type.
21. Rwanbt commented on Oct 17, 2026

    

    Rwanbt

    on Oct 17, 2026

    More actions

    I have a working remote-only Android companion prototype for OpenCode v2 and would like to align with maintainers before sending implementation PRs.

    It reuses the upstream packages/app UI and opencode pair --remote; sessions, agents, tools and models still run only on the PC. Android adds a Tauri WebView shell + HTTPS native transport, not a separate auth system or local execution engine.

    Prototype: https://github.com/Rwanbt/unifia/tree/feat/upstream-android-remote . Android arm64 APK builds in CI; launcher and existing session views tested on real devices via ADB. Cellular/revocation E2E is not yet certified.

    Would a first-party Android remote companion fit the roadmap alongside Web/PWA and iOS? If so, is packages/mobile reusing packages/app an acceptable direction? I can then submit small PRs for (1) Android shell, (2) secure native network/pairing, (3) mobile lifecycle, and (4) CI/assets/distribution. I will wait for design guidance rather than open one large implementation PR.
22. arch-rogue commented on Oct 17, 2026

    

    arch-rogue

    on Oct 17, 2026

    More actions

    I have used Openchamber on Android beta app and the experience has been stellar so far
23. neriousy

    marked [FEATURE]:apk availability #49316 as a duplicate of this issue on Oct 20, 2026
24. neriousy commented on Oct 20, 2026

    

    neriousy

    on Oct 20, 2026

    Member

    More actions

    Thanks for the request—mobile-friendly web access and an installable PWA are available in 2.0.27. Run opencode pair --remote on your computer, confirm the remote-access prompt, and open the generated link in your phone’s browser; you can add it to your home screen, and your computer must stay running. Update with opencode upgrade or npm i -g @opencode/cli@latest (desktop: update the app). Please comment or reopen if mobile access still does not work on that version.
25. neriousy

    closed this as completedon Oct 20, 2026