Port forwarding overview
Find development ports in a workspace, open them locally, and manage the processes behind them.
On this page
Every Glueprint host finds listening TCP ports that belong to your work and lists them in the workspace Ports popover. Open it with the plug icon. A dot badge appears on the icon when something is listening.
How detection works
Glueprint normally enumerates listening ports every 12 seconds. For one minute after it spawns a terminal, task, or agent session — or after task or agent output mentions a localhost URL — it scans every 2 seconds.
To decide which worktree owns a port, Glueprint walks process ancestry back to Glueprint-spawned terminals, tasks, and agent sessions, and checks the process working directory against the worktree. It never guesses from a process name.
Ports below 1024 and Glueprint’s own engine and control ports are excluded by design. Glueprint’s control ports are never listed or forwardable. The popover is an inventory of your development servers, not a machine-wide netstat.
Read the port list
Each row shows:
- The port number.
- A label or process name.
- The terminal, task, or agent session that owns it.
- The bind address, so you can distinguish a localhost listener from one bound to
0.0.0.0.
Open and manage a port
- Open — click the globe button to open the port.
- Copy URL — open the vertical-dots menu for the row, then copy its URL.
- Stop process — open the same menu to send
SIGTERMto the owning process. Glueprint first re-verifies that it is still the same process. - Hide/Remove — use the row menu when you do not want the port in the list.
- Refresh — click the refresh button in the popover title row to force a new scan.
- + Add port — manually register a port that detection cannot attribute to your work.
Local port detection and opening work on every plan. No relay is involved.