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.
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.
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.