e39cec3847
- Launch posts claimed Expo SDK 52 but app is on SDK 54 (factual accuracy before public posting — HN/Reddit devs check this) - docs/qa/REPLY-FLOW-E2E-2026-06-08.md: verified send->streaming reply works against the live opencode server via app-identical sdk.ts calls (free model); closes the 'opencode can't reply in CI' residual at the data-contract level - owner-submissions.md: 0.4.3 -> 0.4.4 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2.5 KiB
Show HN: OpenCode Mobile – Android client for the opencode AI coding agent
Title: Show HN: OpenCode Mobile – drive your self-hosted AI coding agent from your phone
Hey HN,
I built a React Native / Expo Android app that lets you control a running opencode session from your phone.
What it does
opencode (sst/opencode, MIT) is a terminal-based AI coding agent — you run it on your laptop or a server, it talks to Claude / GPT-4 / Gemini via your own API keys, and it writes, edits, and runs code through tool calls. The mobile app is a thin HTTP + SSE client that connects to the opencode server process. From your phone you can:
- Watch token-by-token streaming output as the agent reasons and codes
- Review inline file diffs before they're committed
- Approve or reject tool calls (file writes, shell commands) in real time
- Start, resume, and switch between sessions
- Connect over local Wi-Fi, Cloudflare Tunnel, ngrok, or Tailscale
Why I built it
I run long opencode sessions that outlast my desk time. I wanted to check in from the couch, approve a tool call, and let the agent keep going. Every alternative — SSH + terminal app, plain Claude/GPT apps — loses the structured session state. The opencode HTTP API is already there; the phone just needed a proper client.
How it's built
- React Native + Expo SDK 54, TypeScript throughout
- SSE streaming via
EventSourcepolyfill (React Native lacks a native one) - Diff rendering with a custom line-level parser; no WebView
- Biometric auth via
expo-local-authenticationgates the app and individual sends - Credentials in iOS Keychain / Android Keystore via
expo-secure-store - CI builds a signed AAB on every tag via GitHub Actions + EAS
What it is not
It's not a standalone AI model and not a code editor. You need a running opencode server. If you already use opencode, setup is: npm install -g opencode-ai && opencode serve, then paste the URL in the app.
Status
Stable on Android. MIT licensed. Available now via a self-hosted F-Droid repo or a direct signed APK. Google Play is in internal testing and not public yet.
Source: https://github.com/dzianisv/opencode-mobile Landing page (all install options): https://dzianisv.github.io/opencode-mobile/ F-Droid repo (add this URL in an F-Droid client): https://dzianisv.github.io/opencode-mobile/fdroid/repo Direct APK: https://github.com/dzianisv/opencode-mobile/releases/latest
Happy to answer questions about the SSE streaming implementation, the Expo build pipeline, or the opencode API surface.