# How to preview a remote dev server in T3 Code

Review an agent-built UI on an owned development host with T3 Code 0.1.11, and know when to use the shared browser or a desktop port forward.

By Paras Madan | 2026-11-21


When a coding agent says the app is ready at `localhost:5173`, there is a question hidden in that address: whose localhost? If the agent started the server on a remote development machine, typing the address into your laptop's regular browser can show an old local build or nothing at all.

[T3 Code 0.1.11](https://github.com/pingdotgg/t3code/releases/tag/v0.1.11), released November 20, brings remote dev-server access to its in-app browser and adds desktop port forwarding. The useful workflow is to review the exact build the agent started without publishing the development server to the internet.

## Start with a preview you can identify

Use an app you own on a development host you already control. For a first pass, pick a demo route with fixture data and no production sign-in. Have the agent report the name of the environment, the worktree or commit, and the exact preview path after starting your normal development server.

Make the build recognizable. A preview banner, a visible fixture value or the specific copy you changed is enough. A tab that loads successfully is not proof that it is showing the branch under review, especially if you have multiple worktrees running the same app.

T3 can infer candidates from ports opened by terminals and agents. The [tagged remote-access guide](https://github.com/pingdotgg/t3code/blob/v0.1.11/docs/user/remote-access.md#local-servers) notes that discovery does not check whether the port actually serves a web page. Set the project script's **Preview URL** when there is a specific route to review.

## Use the shared tab to review together

If the agent has already opened a preview, start with that tab in the remote environment's **Browser** panel. In the [shared browser implementation](https://github.com/pingdotgg/t3code/pull/15328), the browser runs on the environment host and streams the tab to remote clients. The agent and the reviewer can see the same page. Read-only connections can observe; operating a tab is a separate permission.

This works well for something like reviewing a new empty state. Have the agent leave the shared tab on a fixture with no rows. Check the layout and copy yourself, then give feedback using the route and visible element names. If you need to operate the agent's tab, take control before interacting, then release it when you are done.

## Know what opening your own tab changes

A fresh tab you open yourself in the desktop app for another environment is not the same as looking at the agent's streamed tab. According to the [versioned browser guide](https://github.com/pingdotgg/t3code/blob/v0.1.11/docs/user/remote-access.md#browser-on-a-remote-environment), that tab renders on your computer, but its local development address still goes to the remote host through T3's connection. This lets you use the desktop preview's own selection and annotation features.

Use the shared tab for reproducing what the agent sees. Open your own tab when you want to inspect the same route independently. Do not assume two tabs share a signed-in state or the same fixture navigation. Put the expected route in your review notes so the next person can start in the right place.

## Forward one port only if you need an external browser

The [desktop forwarding change](https://github.com/pingdotgg/t3code/pull/39393) adds a control in the thread's **Servers** list. For an external-browser check of your own demo, use it on the known development port and open the address T3 reports. If that port is already occupied on your laptop, T3 chooses an available one. The displayed port, not the host's original number, is the address to use.

The forward listens on the laptop's loopback interface, not the network. It is still reachable locally, so stick to the demo server rather than forwarding admin panels, databases or services with real customer data. Skip this step entirely if the in-app preview is enough.

## Close the path when the review ends

Stop the forward from **Forwarded ports** in the command palette. Quitting the desktop app also ends forwards. Stop the development server separately if no one needs it anymore.

In the thread, leave the build identifier, the route you reviewed and what you saw. That gives the next reviewer evidence they can trace back to the right build. The localhost link alone does not.

## Explain the workflows your product makes possible

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help developer tool teams turn releases like this into technical writing and product stories that show what changed and how to put it to use.

[Book a 30-minute call](https://cal.com/paras-madan/30min).
