I Built a Cloud Terminal Because I Was Tired of Babysitting My Laptop
Source: Dev.to
Overview
For the last 8 years I’ve been building software mostly inside terminals—SSH sessions, long‑running scripts, AI agents, deployments, background workers. The recurring annoyance was that closing my laptop, losing internet, logging out, or switching devices would kill everything: processes died, sessions broke, progress vanished.
So I built something to fix that.
The Problem
- Most of us use a local terminal and SSH into servers.
- We may rely on
tmuxorscreen. - Even with those tools, we’re still tied to a specific machine. If the laptop shuts down or we move away, we’re limited.
I wanted
- Sessions that never die
- Device independence
- Real‑time sync
- No babysitting my laptop
The Idea
A cloud‑hosted terminal where your sessions run on a server, not in your browser or on your local machine. If the browser disconnects, the process keeps running. If you log out, it keeps running. Switch devices, reconnect, and continue exactly where you left off.
How It Works (High Level)
- Persistent PTY layer
- Server‑side session management
- Secure WebSocket communication
- Encrypted sensitive data storage
- Per‑user isolated sessions
The browser is just a window; the actual shell runs in the cloud.
Security
- HTTPS and secure WebSocket connections
- Encrypted sensitive data
- Isolated sessions per user
- Optional server lock and inactivity auto‑lock
You can test it on non‑critical servers first if you want to evaluate it.
It Is Live
I started building this about a month ago, and now it’s live.
I would genuinely love feedback from other developers—especially those who live inside terminals daily. If you have thoughts, concerns, or ideas, I’m open. Let’s build tools that make our lives easier.