Skip to content

Share a Local App with Clients

CloudLink turns an app that is already running on your machine into an HTTPS link a client can open in a normal browser. Nothing is deployed. This guide is the independent workflow: no OpenCode or OpenCode Mobile is required.

  • An app listening on loopback, for example http://localhost:5173.
  • A CloudLink account and active subscription.
  • The CloudLink connector for macOS, Windows, or Linux.
  • A machine that can stay online while the client uses the link.
  1. Open app.opencodecloud.link.
  2. Sign in with your email address. The console sends a single-use sign-in link.
  3. Start the subscription from the account page with Stripe. If browser billing is unavailable, subscribe in OpenCode Mobile.

If you already subscribed through OpenCode Mobile, keep that subscription. The mobile app can link an existing store subscription to a browser account; follow the instructions shown in the app.

  1. Download the package for the operating system from Downloads or the install overview.
  2. Open the connector. It shows a one-time pairing screen.
  3. Open the activation link in your browser, or scan the QR code in OpenCode Mobile if you use it.
  4. Approve the claimed device on the machine. The tunnel does not start until you approve.

Pairing codes are single-use and expire after five minutes. See Pairing and activation.

Start the development server the way you normally do, for example:

Terminal window
npm run dev
# Local: http://localhost:5173

The service must listen on 127.0.0.1 or ::1 on an unprivileged port from 1024 to 65535. A hostname, a private network address, or a cloud metadata address is rejected.

  1. Open Settings → Services in the connector.
  2. Choose Add service.
  3. Set a name, an ID, and the public HTTPS port. Leave Path empty when the app emits absolute asset URLs.
  4. Set Target to the loopback address, for example 127.0.0.1:5173.
  5. Save. The service starts disabled and private.
  6. Enable it, then use Probe to confirm the local target is reachable.

The public URL uses one of Cloudflare’s supported HTTPS ports:

https://m-7f3a91c2.opencodecloud.link:8443/

A root service owns the port. A service with a path shares the port with other path services:

https://m-7f3a91c2.opencodecloud.link:8443/preview/

See Exposed services for the full field reference.

Mode Who can open it
Private A paired device or the connector’s browser credential
Public link Anyone with the managed share link
Password protected Anyone with the share link plus the visitor password

For a public-link or password-protected service, choose an expiration:

  • 15 minutes
  • 1 hour
  • 24 hours
  • A custom duration from 1 minute to 366 days
  • No expiration

A password must be 8–128 characters. It is write-only: store it in your password manager before saving. The share link contains a token; send the link and the password in separate messages. Apply the access settings to create or replace the managed share link.

New services are private and disabled until you explicitly change them. A public or password-protected service is reachable only through its managed share link after the policy is applied.

  1. Copy the share link.
  2. Open it in a private browser window before sending it.
  3. Check the app’s assets, navigation, API calls, and WebSocket connections.
  4. Send the link through the channel you normally use with the client.
  5. For a password-protected service, send the password separately.

A public-link service does not require the client to install anything or create an account. A private service requires CloudLink credentials. A password-protected service asks for the visitor password.

Changes to service settings apply live without restarting the tunnel. To end a review:

  • Revoke sharing ends the managed link and visitor sessions for that policy revision.
  • Change the password invalidates existing visitor sessions that used the old password.
  • Disable the service stops forwarding traffic.
  • Remove the machine in the browser console or mobile app retires the tunnel and DNS record.

Stopping the connector or taking the machine offline also makes the link unavailable. The machine must be online for a client to use it.

  • The app is running and bound to loopback.
  • The service is enabled and the tunnel reports connected.
  • The public URL opens in a private browser window.
  • Absolute assets load; use a root service if they do not.
  • Private, public-link, or password access is the mode you intended.
  • The expiration matches the review window.
  • The client has the link, and the password separately if needed.
  • The machine will stay awake for the review.
Symptom Check
URL returns authentication The service is private; use CloudLink credentials or change the access mode
Password page rejects the visitor Confirm the password was saved after the latest change
Assets or redirects break Use a root service, or review Keep path prefix
Service unreachable The app is stopped, bound elsewhere, or using the wrong port
Port rejected Use 8443, 2053, 2083, 2087, or 2096
Link stops working The connector or machine went offline, or the share expired
Changes do not apply Save the service and probe the target again

For more, see Troubleshooting and Security and privacy.

CloudLink (OpenCode Cloud Link) is an independent product. It is not built by the OpenCode team, is not endorsed by them, and is not affiliated with them in any way. See thePrivacy Policy andTerms & Conditions.