remotecodeA remote. Not another backend.
Your computer does the work.
RemoteCode is a native phone interface for an existing compatible OpenCode V2 backend. It doesn't move your projects to this website or start a separate coding service for you.
This page explains the intended workflow, not an invitation to install an unverified package. Official release links and supported versions will be listed here when ready. Don't download unofficial APKs or paste credentials into this website.
1. Keep OpenCode on Ubuntu
Use your existing OpenCode installation and its compatible V2 backend. Your computer must remain powered on, with OpenCode and the selected connection available. Your existing AI provider configuration continues to apply.
2. Choose how to connect
On your local network: the Ubuntu companion can expose an explicitly approved private HTTPS listener. Pairing includes the computer's certificate identity so supported Android builds can verify the connection. Local access doesn't require Tailscale.
Away from your desk: the documented remote setup uses your own Tailscale connection. Tailscale is installed and configured separately; RemoteCode is not a VPN. Do not expose an unauthenticated OpenCode endpoint to the public internet or disable certificate verification to make a connection work.
3. Pair deliberately
Open the Ubuntu companion and choose Pair a phone. Scan its short-lived QR in the phone app and confirm the computer. Enabling local network access is a separate action; generating a pairing QR does not enable it automatically. Never share QR contents, pairing codes or access tokens in screenshots, email or social messages.
4. Read, review and follow up
Open a session to read messages and activity. Queue or steer follow-ups, answer questions and review permission requests. Actions are sent to the selected computer; they can change real project files. Keep backups and only approve work you understand.
Optional extras, not prerequisites
- Local tray alerts: opt-in phone notifications while relevant app screens are active.
- Background push: a separate Firebase-configured build and notification helper are required. Delivery depends on Google services, network and device policies.
- Wear OS: an experimental companion for an explicitly approved watch. It needs the paired phone online and cannot replace the phone's connection.
There is no account signup, checkout or installer on this website. For release questions, email Jared Ringenberg. Read the privacy notice before configuring optional services.