Termexo v0.10.0: reach your desktop workbench through your own relay
Your coding agent is still working on your desktop when you leave. Termexo v0.10.0 lets you reconnect to that same workbench from a phone or another computer, across networks, through a self-hosted relay.
The desktop opens an outbound tunnel, so it needs no public IP or router port forwarding. Open the relay address in a phone or another computer’s browser to check terminal output, respond to your agent and keep working in the same workbench.
Self-host termexo-relay, enroll your desktop with a code or account, then open its address or QR code. The relay supports Linux, macOS and Windows, plus containers; the Termexo desktop app is for Windows 10/11 x64.
v2 session traffic uses AES-256-GCM after an authenticated handshake. Relay login and the desktop token are independent access checks. You need a reachable HTTPS relay and a desktop that stays on with Termexo connected.
What would you use this for first: checking a long-running agent, answering its next question, or continuing from another computer?
Release: https://github.com/gemron/Termexo/releases/tag/v0.10.0
Self-host the relay: https://github.com/gemron/termexo-relay
Published by the maintainer with AI-assisted writing. Illustration is an AI-generated concept, not a product screenshot.
Replies
The Caddy and nginx examples are good. What's missing is th people who already have a proxy on 80 and 443. My VPS runs Coolify, so Traefik owns both ports and the relay would go in as one more container with --tls off. A Traefik labels example next to the Caddy one would save that crowd an evening, including what --trusted-proxy should be inside a Docker network.
Also Coolify generates the same redirect-to-https middleware name for every app. Once their configs drifted, Traefik discarded the middleware and dropped every router that used it. All 13 apps on the box lost the http to https redirect, and nothing in the UI said so. Someone typing the relay address without https:// would just get a 404.
So I'd add one line to the docs: after deploying, open the plain http address once and check it redirects