Support

One mailbox, read by the person who wrote the thing: [email protected]. No ticket system, no bot, no account to create — and no promise of a reply within any particular number of hours.

Reporting a bug

What makes a report actionable: what you were connecting to (the kind of server, not its address), what you expected, what happened instead, and your Chrome version. If the terminal printed an error, paste it — but read it over first for hostnames and usernames you would rather not send.

Abuse and privacy

Someone using our relay to reach your server, or a question about what we keep: [email protected]. For an abuse report, include the destination address and a timestamp with a time zone — the relay's journal is keyed by destination and time, and 30 days is as far back as it goes.

Answers to the three most likely questions

The icon disappeared after I installed it

Chrome hides new extensions behind the puzzle-piece icon in the toolbar. Click it, find SSH Terminal, and pin it — with pictures, here.

Can I avoid your relay?

Yes. Settings → Relay takes any endpoint you like, and the protocol it speaks is deliberately plain: the extension opens wss://your-relay/connect?host=&port= with the binary subprotocol, and from then on every WebSocket frame is raw TCP payload in one direction or the other. Nothing else is sent, so a websockify-style server in front of your network is enough, and ours never sees the session. Chrome cannot open a raw TCP socket from an extension, so some relay is unavoidable — but it does not have to be ours.

Does it work on a Chromebook or a locked-down work laptop?

That is the case it is built for. There is nothing to install beyond the extension itself, no native host, and no developer mode. If your organisation's policy blocks extensions outright, nothing here can get around that — and should not.