tbase is chat as a filesystem, for teams who live in the shell. Your accounts, your SSH, your permissions. Nothing new to install, learn or trust.
Chat, file transfer, voice, radio, tv and video calls live in one directory tree. Click through it. Every path is real, with the mode bits the server uses.
Every channel has three live feeds. Humans get color and markdown, bots get JSON, agents get clean text. Pipe a feed into a program, or write to send from cron. No SDK, no webhook, no bot token.
$ cat everyone/stream.bot | jq -r .data \
| my-agent > everyone/send
Every request arrives with the caller's uid from the kernel. The server stamps each message with who wrote it and when, and strips terminal escapes on the way in. A private room is its members' names, and to anyone else the path does not exist. The server does not encrypt message content; add end-to-end encryption with age at the client.
$ ls private/ tomo,wren $ ls private/ines,tomo,wren ls: No such file or directory
AGPL-3.0, Go 1.24, Linux with FUSE. People connect with the SSH login they already have.
go build -o tbase-server ./cmd/tbase-server sudo groupadd tbase && sudo usermod -aG tbase wren tbase-server mount /var/tbase -allow-other
Hosted tbase is on the way: your team gets its own isolated tbase server, with accounts, backups and updates handled. Nothing is shared with other teams. Leave your email and you are first to know.
No. If you can ssh in and use echo and cat, you can chat. Voice calls and broadcasts use two small optional clients, tbase-voice and tbase-cast.
People who can log in to the server and belong to the tbase group can read the public channel. A private room is visible only to the members named in its path. To everyone else it does not exist.
Traffic is encrypted in transit because it travels over SSH. The server itself does not encrypt message content, and channel history is stored as plain JSONL on its disk. If you need content that even the server operator cannot read, add end-to-end encryption at the client with age. The docs include a worked example.
Add their account to the group: sudo usermod -aG tbase wren. It takes effect within about a second, with no restart.
Yes, and they are first-class. Write to send to post. Read stream.bot for JSON or stream.llm for plain text. Any program that can open a file can take part.
Each reader gets its own bounded buffer. A slow reader drops only its own oldest messages and gets a marker saying how many it missed. It never slows anyone else down.
10,000 messages per channel by default. Change it with echo 50000 > ctl/retention, where 0 means unlimited.
The server needs Linux with FUSE. The voice and cast clients also run on Windows. You can chat from any machine that can SSH into the server.
ii turns an IRC connection into files on your machine. ssh-chat gives you a chat room over SSH. tbase is the server itself: the files are the chat, and Unix ownership and mode bits are the access control.
tbase is young. The README calls it an experiment in simple file-based interfaces, and the design notes list known limitations. It is open source under AGPL-3.0, so you can read exactly what it does before you trust it.
Each team gets its own isolated tbase server with accounts, backups and updates handled. It is not open yet and pricing is not set. Join the waitlist and you will hear first.