Your ports, where you left them.
If you administer servers, you already have the tunnels memorised — a long ssh -N -L in a terminal you must not close, retyped after every VPN drop. Tunnel Mate keeps them in the menu bar instead, and reconnects them itself.
It does not want to own your SSH setup.
Tunnels are plain ssh -N -L/-R processes. User, IdentityFile, ProxyJump and Port come from ~/.ssh/config and are never copied into the app's own configuration — so there is one place to change a host, and it is the one you already use.
Sessions
One forward: local port, remote host, remote port. Host autocomplete reads the hosts already defined in your SSH config.
Schemas
A named group of sessions that start and stop together — a whole environment brought up in one click rather than four terminals.
Reconnect
Dropped tunnels come back on their own. When one can't, the session carries the last error instead of failing silently.
Restore
Whatever was running when you quit is running again after launch. State lives in ~/.tunnel-mate/.
The parts that matter after week one.
Command palette
Start, stop and jump to any session or schema from the keyboard, without opening the window.
Import and export
Configuration moves as YAML — reviewable in a diff, shareable with a team, restorable on a new machine.
Session logs
Per-session output kept where you can read it, so a refused forward is a question you can answer.
Jump hosts
ProxyJump chains work because they are resolved by ssh itself, not reimplemented.
macOS only, and honest about it.
Tunnel Mate 1.0 is on the Mac App Store. It is macOS only — there is no Windows or Linux build, and no date for one.
If you upgrade from the earlier Electron release, first launch imports ~/.pfm/ once and never writes to it — the old app stays a working fallback.