ANDROID · OPENCODE REMOTE

opencode,
in your pocket.

Your desktop session keeps running. Pick it up on the phone to read output, switch models, run commands, review code or simply talk.

Encryption
Noise NK end-to-end
Host
Linux x64 / arm64
License
Apache-2.0
NOISE NK · E2EE
OC Remote Android session with live messages and tool activity
$ ocremote status

listen    0.0.0.0:8787
direct    ws://192.168.1.42:8787
relay     off
opencode  online
clients   1
SpeakVoice or text input
RunTool calls and queued input
ReviewLive output and line comments
SyncState follows every client

One session, four ways.

Not a shrunken desktop, but a remote session laid out again. Streaming output, commands, review and sync all happen on one screen.

The session stays close

Reasoning, tool calls and queued input are preserved. Keep typing while it runs; the message sends next.

Live output Queued input Bottom sheet
Session settings sheet

Commands keep their names

Aligned with the opencode TUI. Terminal-only commands are greyed out instead of pretending to work.

/models /skills Aliases
Command palette/
/modelsswitch model
/agentsswitch agent
/skillsattach to next message
/statusview session state
/terminalunavailable on phone

Review where the code is

Select a line range and write a comment. Comments merge into one review prompt back in the session.

Line comments Diff Binary guard
Selecting code lines and adding a comment

State follows every client

When another client changes agent or model, the phone updates without a page switch. Deleted sessions return to the empty screen.

Event stream Auto refresh Compaction
event streamshared
agent.selectedbuild → plan
model.selecteddeepseek-v4.1
session.deletedempty screen
No page switch

Three ends, one job each.

The host sits next to opencode, the phone drives the session, and the relay only appears when the network needs it.

Host

Runs beside opencode. The password stays local.

LINUX
Local service registry Noise NK identity
$ ocremote status

listen    0.0.0.0:8787
direct    ws://192.168.1.42:8787
relay     off
opencode  online
./ocremote start && ./ocremote direct 0.0.0.0:8787 && ./ocremote pair

Phone

Scan, pair and verify the fingerprint.

ANDROID
Scan or paste SecureStore token
Pair device04:58
482 913
FingerprintA3:F1:9C:2D
TransportDirect LAN
Verify, then connect
Add host → Connect and pair

Relay

Optional. Forwards ciphertext for remote networks.

OPTIONAL
Noise NK auth Optional TLS 3 hosts · 3 phones each
$ ocremote-relay admin status
{
  "relayId": "relay_4d5b8c0…",
  "v": 3,
  "hosts": 0,
  "maxHosts": 3,
  "maxClients": 3
}
./ocremote-relay --data-dir ./data --listen 0.0.0.0:8443 --public-url ws://<IP>:8443/ws

The relay forwards,
it cannot read.

opencode keeps listening on 127.0.0.1 only. Phone and host speak Noise NK; the relay sees rooms and timing, not code.

  • One-time pairingA short pair code issues a device token after fingerprint verification.
  • A fresh handshake per connectionX25519, ChaCha20-Poly1305, SHA-256.
  • The relay key is pinned in the inviteThe X25519 key ships with the invite; a failed authentication is rejected instead of silently downgraded.
Read the security model →
ANDROIDPhoneSession · commands · review
LOCALHOSTHostopencode · token hashes
Optional relay · sees rooms and timing only
Application data is ciphertext Relay cannot read

Start on the phone,
keep working on the desktop.

Download 1.0.1. Pick the APK for your phone; the host bundle ships Bun and the speech model.

Mobile1.0.1 Host1.0.1 Relay1.0.1
Open the latest release ↗

The current APK uses the Expo debug keystore and needs a production keystore before public distribution. Release builds use the Android system CA store; Noise NK authentication does not depend on certificates.