Integrations

OpenCode is optional. It is still fully supported.

CloudLink shares local apps with clients first. The OpenCode integration is a feature you can turn on when you want agent access alongside the preview, not a prerequisite for using the product.

Two supported ways to run CloudLink

01

Services only

Keep the OpenCode integration off, or runopencode-cloudlink run --no-opencode on Linux. The connector starts no OpenCode process, downloads no OpenCode runtime, and exposes only the loopback services you configure. This is the simplest path for client previews.

02

With OpenCode

Let the connector start and supervise a loopback OpenCode server, or explicitly adopt a server you already trust. You keep the OpenCode web UI window, global configuration editing, mobile pairing, and the local agent MCP. Existing OpenCode users do not need to change their workflow.

What the integration adds

OpenCode Mobile is not required

Create your account in the browser atapp.opencodecloud.link, subscribe with Stripe, install the connector, and open the activation link the connector displays. The pairing is still approved locally on the machine before the tunnel starts. OpenCode Mobile is an alternative client for the same account, not a gate.

If you already use OpenCode Mobile, nothing is removed: your subscription, machines, QR pairing, and thephone-side guideremain available.

Pair a machine

  1. 01

    Create the account and subscription

    Sign in with your email at app.opencodecloud.link and start the subscription. App Store and Google Play purchases from OpenCode Mobile use the same entitlement rows.

  2. 02

    Install and open the connector

    Install the package for the machine that runs your app or OpenCode project. The connector shows a one-time pairing screen when it is ready.

  3. 03

    Claim the pairing

    Open the activation link in your browser, or scan the QR code in OpenCode Mobile. Then approve the claimed device on the machine. The tunnel does not start until you approve.

  4. 04

    Expose a service or use OpenCode

    Add the local app port as a service for a client preview, or keep the OpenCode integration enabled for the web UI and agent workflows.

Related documentation

Common questions

Do I need OpenCode to use CloudLink?

No. Run the connector with the OpenCode integration off, or pass --no-opencode on Linux. CloudLink still provides the tunnel, local service sharing, access policies, and the browser account console.

Do I need OpenCode Mobile?

No. Sign in at app.opencodecloud.link, subscribe, and use the connector activation link to pair a machine. OpenCode Mobile remains supported if you already use it, including QR pairing and machine management.

Does the OpenCode integration change my existing setup?

No. The connector can manage its own loopback OpenCode server, adopt an existing trusted server, or run without OpenCode. Existing OpenCode Mobile users keep their subscription, paired machines, and documentation URLs.

Can an AI agent expose a local service?

Yes. A paired connector exposes a local MCP server to OpenCode agents. The agent can list, expose, enable, disable, and remove services, and receives the public URL. The service is still subject to the access policy you configure.

Is CloudLink built by the OpenCode team?

No. CloudLink is an independent product. It is not built by, endorsed by, or affiliated with the OpenCode team. OpenCode is a separate open-source project.