Why tTerm's code is open, even though paid plans are coming
All of tTerm's code is now under AGPL v3 instead of MIT, and paid plans are coming soon. Here is why one does not get in the way of the other, and why we opened even the server.
Blog
What's new in tTerm
What we have shipped and what has changed. Short notes on every release also go to our Telegram channel.
tTerm now works in the browser
All your servers and computers in one tab, every command in a block of its own, and no keys on your device. What tTerm Web can do today, how to connect a machine and what comes next.
Read the postMore posts
October 2026
Notes, colored projects and terminal names
Runbooks, checklists and notes on access now live next to the machines they are about. You can make projects of your own and give each a color, name your terminals, and move machines and notes from one project to another. Here is what tTerm Web learned in its first days.
Windows on a computer are now independent
On a server, every window has always been a terminal of its own. On a computer with the agent, all windows shared one shell: a cd in one moved the others too, and while a program ran in one window, the rest had to wait. Now each window gets its own shell, the same as on a server. You can keep a dev server running in one window and work in another.
September 2026
You can answer a command while it runs
When a program asked Continue? (Y/n), there used to be no way to reply: your message would not send until the command was over. Now whatever you type while a command is running goes to its input, the way it would in a terminal. The bot marks such a message with 👌.
The agent now runs your shell: bash or zsh
It used to start bash no matter what. On macOS, where zsh has been the default since 2019, that meant somebody else's environment: half of what you had installed could not be found.
tTerm is now a verified organisation on GitHub
github.com/tterm-net carries a Verified badge: GitHub confirmed that the organisation and tterm.net are the same people.
Several terminals per machine
You can now keep more than one terminal open on the same server – one tailing a log, another doing the work. They show up as separate lines in /use, each with its own shell: a cd in one leaves the other where it was.
August 2026
tTerm is live
A terminal for your servers, right here in Telegram. Type a command – it runs on your machine, and the reply comes back as a message with the exit code, the working directory and the git branch. The shell remembers where you left off.
The bot on its own server
The bot moved to its own server and no longer depends on a laptop being open. Source for the bot and the agent is public.
Buttons in messages
Machine list, menus and confirmations moved to buttons inside messages. A machine that cannot be reached is greyed out instead of leading to an error.
Access with a time limit
Shared access with time limits. Expired access closes itself and both sides are told. Owners can export the full command history as a file.
Computers through an agent
Computers can be connected too, through a small agent that dials out. macOS and Linux for now.
New posts reach Telegram too
Short notes on every release in the tTerm channel.