[FEATURE]: Publish OpenCode Mobile for Android (Google Play / beta APK)

Aperta
  • Qualcosa non va?
#62,721 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android, typescript
Ambito
mobile

Direzione di ricerca

Start by reading the Mobile docs at https://opencode.ai/mobile and the existing iOS client distribution setup; the issue does not name repository files or tests. Determine how Android builds, signing, Google Play publishing, and release APKs fit the project’s existing workflow. Done means an Android beta is available through Google Play or as a signed GitHub release APK with checksums and install instructions, with the Mobile docs updated to cover pairing and supported Android versions.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Make OpenCode Mobile available on Android phones.

Right now Mobile is distributed only as an iPhone TestFlight public beta. The docs at https://opencode.ai/mobile list "Google Play (Android, coming soon)" and the setup instructions only describe installing from TestFlight, so Android users have no official way to pair with their computer and steer sessions from their phone. There is no Play listing, no ETA, and no downloadable APK.

Why this matters
  • Android has the larger global install base, and the mobile remote is most useful on the phone people already carry. Today the client effectively ships for one platform only.
  • The pairing flow (opencode pair --remote, --remote over OpenTunnel) and the remote session API are platform-agnostic. The client already exists, so this is primarily a distribution/parity gap, not new protocol work.
  • Users who need Android today are pushed to unofficial community forks that can lag behind the API (for example the permission reply schema change tracked in #62585) and are not supported by the project.
Suggested scope
  1. Publish the Android build to Google Play (internal or closed testing is fine) and link the listing from the Mobile docs page.
  2. Until the Play release is live, publish a signed APK as a GitHub release artifact, with checksums and install instructions, so users can sideload.
  3. Keep feature parity with iOS: QR / one-time-link pairing, session list, streaming transcript, prompt + interrupt, permission approve/deny, voice mode, and background notifications.
  4. Document the minimum supported Android version and any Android-specific pairing differences.
Alternatives considered
  • Running OpenCode itself on the phone via Termux or a Linux wrapper (see #47612 and #60762): different use case, and it does not replace the remote client.
  • The web UI in a mobile browser / PWA: works, but has no native push notifications or secure credential storage and behaves poorly when backgrounded.
Additional context
  • Related: #60762 proposes running the agent inside a Linux wrapper on Android; #47612 asks for Termux compatibility of the npm package. Both are about running the core locally, not about releasing the Android mobile client.
  • Happy to test a beta build on Android hardware and report issues.
Environment (requester)
  • opencode version: 2.2.5
  • OS: Linux x64 (issue filed from a desktop; target platform is Android)
  • Terminal: xterm-256color
  • Shell: /usr/bin/bash
  • Install/channel: latest
  • Active plugins: none found
Lingua principale
TypeScript
Stelle
225k
Fork
30.4k
Merge medio
4h 16m
PR unite (30g)
528

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di anomalyco/opencode

Tutte le issue di anomalyco/opencode

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.