mirror of
https://github.com/l0ng-ai/tty7.git
synced 2026-09-22 16:02:24 +00:00
l0ng-ai
03c3081a6e
A remote workspace's ports were never listed. The pane lives in the peer's registry and QueryProcs asks this machine's daemon, which has never heard of it, so the answer was an empty list — indistinguishable on screen from a pane serving nothing. Add a control request so the peer answers instead, gated on a feature so an older server says "I cannot tell you" rather than "nothing is listening". With the ports visible, the forward becomes something the user should not have to think about: a port opens on a click, and a new one is forwarded unasked, at the same number where that number is free here. The watch runs with the panel shut, which is when a port appearing is most worth saying something about. Ports and Forwards were two sections that never mentioned each other; a row is now a port, and the forward is where that row says it comes out. Adding one by hand asks for one number instead of five fields, with the rest of the ssh -L grammar one disclosure away. Claude-Session: https://claude.ai/code/session_01TPXrptp2rCGKjXaz4xE3Lq
96 lines
3.9 KiB
Plaintext
96 lines
3.9 KiB
Plaintext
---
|
|
title: "Port forwarding"
|
|
description: "Local, remote, and dynamic forwards — preconfigured or added mid-session."
|
|
---
|
|
|
|
## Ports you did not ask to forward
|
|
|
|
When a pane is on a remote machine, tty7 watches what its processes are
|
|
listening on and forwards those ports for you. Start a dev server on the remote
|
|
`:3000` and a moment later a notice says it is at `http://localhost:3000` —
|
|
same number, no rule to write.
|
|
|
|
The **Ports** section of the Info panel is the whole list: one row per listener,
|
|
the process that owns it, and where it comes out on this machine. The globe
|
|
opens it in a browser, the copy tile takes the address that works from here,
|
|
and ✕ takes the forward back down.
|
|
|
|
Ports are forwarded once each. Remove one and it stays removed — the offer is
|
|
made a single time per port, not on every poll.
|
|
|
|
The local port matches the remote one whenever it is free here. When it is not —
|
|
something else on this machine already has `:3000` — the OS picks another and
|
|
the row says which.
|
|
|
|
Turn the whole thing off under **Settings → Terminal → Links → Forward remote
|
|
ports** (`ssh_loopback_forward: false`).
|
|
|
|
<Note>
|
|
In a remote workspace the ports are found by the **`tty7-server` on that
|
|
machine** — the panes are its, and this machine's daemon has never heard of
|
|
them. A server too old to answer says so in the Ports section rather than
|
|
showing an empty list; updating it is what fixes that. Panes that ssh'd
|
|
somewhere from inside a local pane are a different case: those processes
|
|
belong to no tty7 server, so nothing lists them.
|
|
</Note>
|
|
|
|
## The three kinds
|
|
|
|
| | What it does |
|
|
|---|---|
|
|
| **Local** (`L`) | A port on this machine reaches a service on the remote side |
|
|
| **Remote** (`R`) | A port on the remote machine reaches a service here |
|
|
| **Dynamic** (`D`) | A SOCKS proxy on this machine, routed through the connection |
|
|
|
|
## Adding one to a profile
|
|
|
|
**Settings → SSH →** a profile **→ Port forwarding → + Add rule**. Rules saved
|
|
here open with the connection, every time.
|
|
|
|
A Local or Remote rule needs a listen port and a target; a Dynamic rule needs
|
|
only the listen port. An incomplete rule tells you so rather than being saved
|
|
half-configured.
|
|
|
|
Each rule takes an optional description — *"what it's for"* — because six months
|
|
later `8080 → 3000` explains nothing.
|
|
|
|
## Adding one mid-session
|
|
|
|
The **+** on the Ports section — or *SSH: Port Forwarding* in the command
|
|
palette — opens a form asking for one thing: the port the remote is serving on.
|
|
It comes out here under the same number, and the form says so before you commit
|
|
to it.
|
|
|
|
**Advanced** opens the rest of the grammar: remote and dynamic forwards, a bind
|
|
host other than loopback, a target on some third machine, a description. You
|
|
need it about as often as you need `ssh -R`.
|
|
|
|
These live only as long as the session unless you save them into the profile.
|
|
|
|
<Frame caption="Placeholder — screenshot: the Ports section with a forwarded port and a dynamic rule">
|
|
<img src="/images/placeholder.svg" alt="The ports section" />
|
|
</Frame>
|
|
|
|
## Links in the terminal
|
|
|
|
<kbd>⌘</kbd>-clicking a `localhost:PORT` link inside a remote pane opens the
|
|
forward for that port if there is not one yet, then the browser. Same machinery
|
|
as the Ports list, reached from the output instead of the panel.
|
|
|
|
## Jump hosts and proxies
|
|
|
|
Multi-hop connections are configured per profile:
|
|
|
|
- **Jump host** — point at another saved profile, or use a `ProxyJump` chain
|
|
- **ProxyCommand** — an arbitrary transport command, with `%h`, `%p`, `%r`
|
|
substituted
|
|
- **SOCKS5 proxy** / **HTTP proxy** — `host:port`, under **Advanced → Proxies**
|
|
|
|
<Note>
|
|
These proxy settings are for reaching the SSH server. tty7's *own* network
|
|
traffic — update checks, release downloads, remote-server installs — uses
|
|
`http_proxy` in `config.json`, the system proxy, or the `HTTP_PROXY` family.
|
|
Programs running in a pane are unaffected either way; they inherit their proxy
|
|
from their own environment, as in any terminal.
|
|
</Note>
|