# Serverside.chat: Collaborative Terminal-Style Chat for Web Development A shared terminal environment for building small websites together with live collaboration. - **Source:** [Hacker News: Show HN](https://news.ycombinator.com) - **Published:** 2026-09-14 - **Original article:** - **On Brifing:** https://brifing.si/s/1e1a2b25-5e0b-41ef-86a6-69352a3e74e4 ## Introduction to Serverside.chat Serverside.chat is a unique platform offering a terminal-style chat environment designed for collaborative web development. Each room includes a live website, its source history, and a clanker for making changes. The platform uses lightweight WASM VMs to ensure efficiency and constraints, making it ideal for small-scale projects. Users can create up to five rooms, which can be public or private, with varying contribution permissions. ## Keyboard-First Interface The interface is optimized for keyboard use, with commands like Tab to open the room bar and arrow keys for navigation. Typing / in chat reveals available commands such as /invite for contributor links, /mount for filesystem instructions, and /edit to modify room files. This design caters to developers who prefer efficient, text-based workflows over graphical interfaces. ## Room Features and Permissions Rooms can be configured with different contribution policies, from invited members only to open access for any signed-in viewer. Each room includes a shell but restricts arbitrary program execution, focusing on bounded room files and version-control operations. Commands like /permissions and /clanker provide control over room policies and explicit requests for changes. ## SSH and File Access Users can access rooms via SSH on port 2222, with commands like ssh -p 2222 serverside.chat. File operations are supported through SFTP and SSHFS, enabling seamless integration with local workflows. The /mount command also explains WebDAV flow for Finder users, enhancing cross-platform compatibility. ## Browser Interface and API Keys The browser interface runs on port 3000 by default, with optional FIREWORKS_API_KEY enabling clanker functionality. Without the key, basic chat and room services remain operational. This flexibility allows users to choose between full feature access and lightweight usage. ## Room Structure and Guest Handling Each room owns a chat, Git repository, SQLite storage, and temporary previews. Guest sites are accessible via https://room.serverside.chat, while development chats reside at https://serverside.chat/room/room. The host reserves specific paths for deployment selection, ensuring secure and organized guest handling. ## Resource Limits and Security Room repositories are capped at 512 KiB per file and 5 MiB total for working-tree files. SQLite and scratch storage have independent 5 MiB limits. History is linear and rebase-only, with stable and head commits for canonical and HEAD references. Publishing requires owner authority and fast-forwards stable, ensuring controlled updates. ## Why Serverside.chat Matters Serverside.chat bridges the gap between real-time collaboration and web development, offering a constrained yet powerful environment. Its focus on keyboard-first workflows, secure permissions, and lightweight WASM VMs makes it a compelling tool for small teams and solo developers. The platform’s design encourages creativity while maintaining security and efficiency. ## Sources covering this story - https://github.com/bwasti/serverside.chat — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._