I built this because I was tired of SSH-ing into my own computer.

I go by XDope. I am a working developer, not a founder who discovered a market. Termdeck exists because I needed it on a Tuesday and nothing on my disk did the job. If you want the wider picture of what I build and write, that lives on my personal site: bhavikp.in.

There is no team behind this. The whole company is one person, a desktop, a Linux box on the LAN that does the heavy agent work, and a small production server that serves the site you are reading. That is the entire fleet, and it is also the reason the product looks the way it does. I was the first person who had to keep three machines' worth of coding agents straight in their head, and I lost that fight badly enough to write software about it.

Practically, being a one-person shop means two things. Support email goes to the person who wrote the code, so nobody has to translate your bug report twice. And there is no roadmap committee, so if something is broken and small, it is usually fixed the same day rather than filed.

My setup was normal and, I thought, reasonable. Work on the desktop. Run the long, expensive agent jobs on the Linux box because it had the RAM. Keep production on its own server, untouched. Three machines, three shells, and the whole day spent typing ssh at one of them.

It fell apart in the boring way things fall apart. I would start a refactor on the Linux box, walk away, come back an hour later and find the agent had been sitting on a permission prompt for fifty-eight of those sixty minutes, waiting for a keystroke I was never going to see because the window was behind a browser on a different machine. So I did what everyone does: I learned tmux.

tmux genuinely solved the first problem. Sessions stopped dying when my laptop lid closed. But it handed me a stack of new ones. I had to learn a prefix key and then relearn it every time I went a fortnight without detaching anything. Panes let me watch two agents at once, right up until there were five, at which point I was cycling through a grid squinting for the one with a blinking prompt. And there was no way, none at all, to be told anything. tmux has no notion of a notification. It cannot tap you on the shoulder. It will happily hold a finished run in a detached session for six hours and never say a word.

The last straw was reach. To touch the Linux box from anywhere but my desk I had to wire the whole thing up: an SSH key on every device, a private VPN so the box was addressable at all, dynamic DNS because the home IP moved, and a mobile SSH client that turned a coding agent into eighteen columns of wrapped text on a phone screen. I once spent a Sunday debugging my own VPN config instead of the bug I had actually sat down to fix. That was the afternoon Termdeck started.

So the design brief was short, and it was written entirely out of spite: I should be able to open a normal browser tab, on any device I own, and see every agent on every machine, and the ones that need me should come find me.

Termdeck is operated by a Wyoming limited liability company. The terms you agree to when you create an account, the way any dispute is handled, and the obligations owed to you as a customer are all governed by the laws of the State of Wyoming, and that stays true whichever country you happen to be connecting a machine from.

That was not an accident of paperwork. Wyoming passed the first LLC statute in the United States in 1977, and four decades later it still does the thing that mattered to me: it does not require member and manager names to be listed in the public record, and it has no state income tax to complicate a business this small. For a one-person company whose entire pitch is your code never leaves your machine, incorporating somewhere that treats privacy as the default rather than a paid upgrade was the only version that was internally consistent.

The practical shape of that promise is architectural, not legal. Your coding agent runs on your own hardware, signed in with your own subscription, and the transcript files it writes stay on that disk. Termdeck reads them through the agent you installed and paints them in your browser; it keeps no transcript of its own. There is no copy of your repository sitting on a server of mine to be leaked, lost, or handed over.

Questions about the entity, the governing law, or what is stored and where go to [email protected] and reach me, not a queue.