When Claude Code starts a development server on a remote machine, its localhost address belongs to that machine—not the laptop where you open a browser. For a host you can access over SSH, a local SSH tunnel can let your browser reach the remote development server without publishing it on the internet.
This is a private preview workflow for an ordinary SSH-accessible host. It is not a universal recipe for every managed Claude cloud environment, and it does not publish a finished website.
First confirm the server on the remote host
Ask Claude to report the project directory, startup command, listening address, port, and any startup error. Use the project's documented command rather than assuming every app uses the same package manager.
For an HTTP server listening on remote port 3000, check from the remote terminal:
An HTTP response establishes that something answered; a login redirect, error response, or unsupported HEAD request needs interpretation. A connection failure means there is no reason to troubleshoot your laptop's browser yet. Check whether the server started, uses another port, or runs inside a container with a different network boundary.
Open a private tunnel from your computer
Run this in a terminal on your own computer, replacing user@remote-host with your authorized SSH account and host:
The OpenSSH manual documents local forwarding with -L and tunnel-only operation with -N. Here, local port 3001 forwards to port 3000 as seen by the remote SSH host. The explicit local loopback address avoids listening on every network interface.
Keep that terminal open, then visit http://127.0.0.1:3001 in your local browser. The port numbers are examples; match the actual remote service and choose an unused local port. Verify an unfamiliar host's fingerprint through your administrator or provider rather than disabling SSH host checks.
Diagnose the layer that failed
Do not expose the server publicly or disable application security controls as a blanket fix. A tunnel opening successfully does not establish that its destination application is healthy.
If you already use VS Code Remote-SSH, its Ports view provides a forwarding interface. Use the local address it actually reports; it may select a different local port.
Keep preview and publication separate
A private development preview is for checking work. It is not a durable public URL, and it stops being usable if the required server or tunnel stops. Before sharing more broadly, check authentication, secrets, data, and the intended audience. The preview, publish, and export guide explains the different delivery choices.
For Agent.Space cloud Workspaces, the preview and sharing manual describes file previews, development previews, and member site previews. Its site-publishing instructions do not apply unchanged to computer Workspaces, which currently do not offer the same Sites entry.
Choose the Agent.Space path that fits the result
If your work is already in a cloud Workspace, open Agent.Space, find the saved result, and use the appropriate preview before publishing anything. This keeps review connected to the project rather than treating a chat reply as the finished artifact.
If you need to inspect the actual browser on a connected Mac, explore Remote Screen instead. It operates the remote desktop; it is not an automatic public tunnel for every app. Choose it when desktop access is what you need, not simply because a localhost link failed.