---
title: "What is OpenCode Cloud Link?"
description: "Learn how the Cloud Link connector publishes an OpenCode machine to the mobile app, what stays local, and when to use it instead of your own tunnel."
canonical: "https://opencodecloud.link/docs/introduction/"
lastUpdated: "2026-10-19"
---
OpenCode Cloud Link connects the OpenCode server on your machine to the
OpenCode Mobile app. Install the connector, pair it once with your phone, and
your machine stays reachable while your code, models, and prompts remain local.

Cloud Link is **not** a hosted AI service, a replacement for OpenCode, or an
official OpenCode product. It is an independent, closed-source commercial
connector that makes a machine reachable.

## What Cloud Link adds

- **A managed tunnel.** Cloud Link provisions and supervises a named
  Cloudflare Tunnel, including DNS and TLS. You do not need a Cloudflare
  account, port forwarding, or a tunnel configuration.
- **Pairing you approve.** A phone claims a one-time QR code, then the machine
  operator sees the device name and approves it before the tunnel starts.
- **Per-device credentials.** Each phone receives a signed, machine-scoped
  credential with an expiry. The connector verifies it locally.
- **A stable address.** One installation keeps one opaque
  `m-<random>.opencodecloud.link` hostname across restarts, upgrades, and
  re-pairs.
- **A local service gateway.** Publish a loopback dev server, API, or dashboard
  through the same tunnel on a separate origin. Services are disabled and
  private by default.
- **A tray app.** Open the managed OpenCode web UI, edit the global OpenCode
  configuration, control browser access, and opt into start at login.
- **Supervised startup.** Logins, reboots, and network changes are handled
  without manual tunnel restarts. Transient failures retry with capped backoff.

## What stays on your machine

The connector starts and supervises OpenCode bound to loopback. Your
repository, provider keys, terminal output, prompts, responses, and file
contents never pass through the Cloud Link control plane.

The control plane stores connection metadata: account identifiers, machine and
tunnel names, pairing records, and subscription status. Cloudflare terminates
TLS at its edge while delivering the connection; there is no separate
application-layer end-to-end encryption.

See [Security and privacy](/docs/security/) for the full model.

## How it differs from OpenCode's built-in remote access

OpenCode can expose a server directly with `opencode pair --remote`. Cloud Link
runs alongside that feature and adds:

- approval on the machine before the tunnel starts;
- per-phone signed credentials with an expiry;
- a separate, regenerable credential for remote browsers;
- a stable hostname across re-pairs;
- loopback service exposure on separate origins;
- supervised retries and a tray interface.

If the built-in path already meets your needs, you do not need Cloud Link. If
you want managed pairing, credential separation, and service exposure, use
Cloud Link.

## Supported platforms

| Platform | Package | App |
| --- | --- | --- |
| macOS 15+ | Universal DMG (Apple silicon and Intel) | Menu-bar app |
| Windows x64 | NSIS installer | System-tray app |
| Linux x64 | Headless archive | CLI and optional systemd user service |
| Linux ARM64 | Headless archive | CLI and optional systemd user service |

Every desktop and Linux download bundles pinned OpenCode and cloudflared. See
[Install overview](/docs/install/) for requirements and verification.

## Requirements at a glance

- An active Cloud Link subscription, purchased or restored in the OpenCode
  Mobile app from the App Store or Google Play.
- OpenCode Mobile installed on an Android or iOS device.
- A machine that can run OpenCode and reach the internet.
- A working network connection on both the phone and the machine.

## Next steps

- [Quick start](/docs/getting-started/)
- [Install overview](/docs/install/)
- [Pair with OpenCode Mobile](/docs/pairing/)
- [Features](/docs/features/)