Built-in browser on the localhost of an SSH host
- Desktop app
- All plans
What it does
In a project whose agents run on an SSH host, localhost, 127.0.0.1 and [::1] open that host in the built-in browser, for you, your agents and the QA Bot, with no port to forward by hand. The URL stays the same, so cookies, OAuth callbacks and hot reload work. Public addresses still leave from your computer. A local project changes in nothing.
Where to find it
In the built-in browser of a project on a host (see Remote SSH Offload): the via <host> chip next to the address bar, shown on local pages.
How to use it
- Start your dev server on the host: a terminal of the project, a dev command, or ask an agent.
- Open
localhost:3000in the built-in browser. The SSH tunnel opens by itself and the page of the host appears. - An agent does the same with
browser_navigate, and its screenshots show the host's page.
To open your computer's localhost in this project, click the chip: it becomes this computer. Click again to go back. The other pages of the project keep working either way.
The tunnel closes about 30 seconds after no tab shows a page of the host. Nothing runs before the first local page.
Settings
browserLoopback(project, chip next to the address bar: via <host> / this computer, alsosettings_set):host(default) orcomputer, whatlocalhostopens in this project's built-in browser. Synced with your account. No effect on a local project.
Agent tools (MCP)
browser_navigate and the other browser tools follow the project's route. A failed page answers the cause in words ("Nothing is listening on localhost:3000 on the SSH host...", "refuses SSH port forwarding..."), not a browser error code.
Providers
All providers for you: the browser does not depend on the CLI. An agent drives it when the AgentsRoom tools reached the host (see Remote SSH Offload).
Mobile
Not on the phone. Its tunneled preview reaches a server of the computer, not of the host.
Limits
- Plain SSH connections only. AWS SSM and WinRM have no tunnel:
localhoststays on this computer, and the chip says so. - Port forwarding must be allowed on the host (
AllowTcpForwarding). - A password connection needs a saved password, or on macOS and Linux an open terminal on the host. Otherwise use a key or an SSH agent.
- A public page shown in this browser cannot reach the host's
localhost: a tool hosted online that callslocalhostneeds this computer. - An agent on another computer of your account (Remote Fleet):
localhostis this computer, and the chip says so. - Your system browser opens this computer's
localhost, so its button is disabled on a page of the host.
Common questions
- Can the built-in browser open the dev server I started on the host? Yes, with no port to forward. Check the via <host> chip next to the address bar.
- How do I open my computer's localhost in a project on a server? Click the via <host> chip: it becomes this computer, for this project, and follows your account.
- The browser says "Nothing is running on port 3000 of <host>". The tunnel works, but no server listens on that port of the host. Start it there, then Retry. Started it on your computer? Click Use this computer's localhost.
- The browser says "<host> refuses SSH tunnels". Set
AllowTcpForwarding yesin/etc/ssh/sshd_configon the host and reload sshd, then Retry. - The browser says "<host> does not answer". The SSH connection is down or the machine is off. Check your network or VPN, then Retry.
- Do public sites go through my server? No. Only
localhost,127.0.0.1and[::1]do, and a site sees your computer's address. - Is the tunnel a security risk? It listens on
127.0.0.1only, for as long as a tab shows a page of the host (plus 30 seconds), and a public page cannot use it. While it is open, any program on your computer can reach the host'slocalhost, like with a manualssh -D. On a computer shared with other users, keep this computer selected.