c9a57901c4
* chore: repoint OpenCode links to agentlabs.cc/opencode agentlabs.cc/opencode and /opencode/privacy are now live (200). Repoint README, distribution listings (Play/App Store/F-Droid/IzzyOnDroid/iOS), docs, and in-app privacy links (settings + telemetry consent) from www.vibebrowser.app/opencode to the canonical agentlabs.cc hub. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(ci): run local opencode server for CUA smoke true-E2E (#15) GitHub-hosted runners can't reach the Tailscale dev server (100.108.64.76:4096), so the CUA smoke always failed at session creation. - Install opencode-ai and run `opencode serve` on the runner host; the Android emulator reaches it via 10.0.2.2. OPENCODE_URL now points there. - Healthcheck /global/health before launching the app; dump server log on failure for diagnosis. - Add --only-connect-scenario to the smoke script and run just the connect-and-verify-sessions path in CI: deterministic, needs no model backend. The scenario now creates a session if the list is empty, so a fresh server still yields a non-empty list. This makes the smoke a true E2E and also exercises the #10 sessions-list rendering path against a real server. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(ci): emulator smoke script is dash, not bash — drop brace-group healthcheck android-emulator-runner runs the script: block under /usr/bin/sh (dash). The multi-line `|| { ...; }` healthcheck was a dash syntax error (end of file unexpected), failing the step before the smoke ran. Replace with a non-fatal one-line re-check; the server was already health-gated in the prior step. * docs(tasks): record smoke CI round 1 failure + dash fix --------- Co-authored-by: engineer <engineer@opencode.ai> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
3.7 KiB
IzzyOnDroid Inclusion Request
File this as a new issue at: https://codeberg.org/IzzyOnDroid/repodata/issues
Use the text below (starting from "---") as the issue body. Replace all
<PLACEHOLDER> values before filing.
App submission: OpenCode Mobile
App name: OpenCode Mobile
Package / App ID: ai.opencode.mobile
License: MIT
Source code: https://github.com/dzianisv/opencode-mobile
GitHub releases: https://github.com/dzianisv/opencode-mobile/releases
Release URL pattern
APK attached to each GitHub release tag following the pattern:
https://github.com/dzianisv/opencode-mobile/releases/download/<TAG>/app-release.apk
Example (first production release):
https://github.com/dzianisv/opencode-mobile/releases/download/v0.2.4/app-release.apk
Note: IzzyOnDroid should use the GitHub releases tag pattern for auto-update
polling. The app uses semantic versioning (vX.Y.Z tags).
Signing key SHA-256 fingerprint
0C:25:9D:94:E0:FF:EA:5D:63:19:61:4B:22:9D:4B:6B:DC:22:DE:1F:56:E3:8E:76:94:83:98:D2:DF:6A:A0:99
This is the production-release.jks key used for all distribution channels (Play Store, F-Droid, and IzzyOnDroid use the same signing key — users can update in-place across stores).
Description
OpenCode Mobile is a free, open-source (MIT) client for the opencode AI coding agent (sst/opencode). It lets developers connect to their self-hosted opencode server and drive AI-powered coding sessions from their Android phone.
Key features include streaming chat with the AI agent, a file diff viewer for reviewing proposed code changes before accepting them, multi-session management, tool call approval gates, and biometric unlock. All AI traffic flows directly from the app to the user's own server — no middleman, no mandatory accounts, no vendor lock-in. Crash reporting via Sentry is opt-in with default OFF.
The app is aimed at developers who run opencode on a workstation or self-hosted server (on-prem or any cloud VPS) and want a mobile companion for on-the-go session management. An optional hosted "opencode Cloud" backend is planned as a future paid service, but the client is and will remain free and open source.
Anti-features acknowledgment
NonFreeNet applies: the app connects to a user-self-hosted opencode server which may in turn connect to proprietary AI APIs (OpenAI, Anthropic, Google Gemini). The app itself contains no proprietary network code and does not require any specific provider.
No other anti-features apply:
- No ads (no ad SDK present)
- No tracking (Sentry opt-in, default OFF — user must explicitly enable)
- No non-free dependencies beyond FCM receiver classes compiled in by
expo-notifications(local-only usage;scheduleNotificationAsynconly; nogetExpoPushTokenAsync/getDevicePushTokenAsynccalls) - No subscription / license checks in the client
FOSS confirmation
- Source code is fully public: https://github.com/dzianisv/opencode-mobile
- License: MIT (https://github.com/dzianisv/opencode-mobile/blob/main/LICENSE
or inferred from package.json
"license": "MIT") - No proprietary SDKs are required for core functionality
- The APK on GitHub releases is signed with the key fingerprint above
F-Droid mainline track note
A parallel F-Droid mainline submission (MR against fdroiddata) will be filed after the first Play Store release is live. Per IzzyOnDroid policy, IzzyOnDroid will auto-delist this app once the mainline F-Droid repository accepts it. We will notify the IzzyOnDroid team via this issue when that happens.
Contact
Developer: VIBE TECHNOLOGIES, LLC Email: support@vibebrowser.app Website: https://agentlabs.cc/opencode Privacy policy: https://opencode.vibebrowser.app/privacy