Ports
While Claude Code or Codex is building a web app on your server, you'll often want to actually see it — the dev server on :3000, the API on :8080, a Storybook, a docs preview. Ports lists every port your server is listening on and opens any of them over HTTP in an in-app browser, tunneled through your existing SSH connection.
Traffic is forwarded through SSH, so the port does not need to be exposed to the internet — services bound to the server's localhost work too. No firewall changes, no reverse proxies.
Where to Find It
- Server detail page — tap Ports in the Tools section (next to Terminal and VNC).
- Terminal session page — open the top-right menu (⋯) and tap Ports. This reuses the session's connection, so the list opens instantly while the agent keeps working.
Opening a Port
The Port Access sheet lists every TCP port currently listening on the host, with the owning process name and bind address where available.
Tap a port. ServerCC sets up an SSH local forward on a dedicated connection and opens the page in an in-app browser.
The In-App Browser
- Back / Forward — Full navigation with buttons and edge-swipe gestures
- Desktop Site — Switch the Page View between Mobile Site and Desktop Site to test both layouts
- Orientation — Temporarily unlock Landscape for wide layouts, even though the app itself is portrait-only
- Reload — Pull the latest build output after the agent makes changes
Good to Know
- HTTP only — the tunnel always loads
http://. Point it at plain-HTTP dev servers; HTTPS-only services aren't supported. - One tunnel is active at a time — opening another port closes the previous one.
- Port forwarding runs on its own SSH connection, isolated from the terminal — heavy page loads can't stall your Claude Code/Codex session.
- If nothing is listening, you'll see No Accessible Ports — start your dev server first, then pull to refresh.
See also: VNC Remote Desktop for viewing a full desktop instead of a single web page, and Terminal for the session the preview usually accompanies.