More people are running long-lived, interactive processes on their own servers now. Not just developers—anyone experimenting with agentic AI, automation, or self-hosted tools is spinning up a Mac Mini or a cloud VM and working directly from the CLI. But managing those workflows is still awkward. SSH works—but it’s built around sessions that are tied to a specific client. That doesn’t map well to workflows where your terminal session itself is long-lived and context matters. You start something on your desktop, switch devices, and suddenly you’ve lost your working context. So I built PuTTrY. It’s a self-hosted, browser-based terminal designed for persistent, interactive shell sessions across devices. Core idea: Decouple the terminal interface from SSH credentials. – Terminal sessions live entirely on the server (not your client) – Resume the same interactive context from any device – No SSH setup or key management per device – Auth and access handled centrally Architecture (high-level): – Server-side terminal sessions (SSH-equivalent permissions) – WebSocket streaming between browser and backend – Single-user per instance (runs in your home directory) – Guest links for secure, controlled session sharing Works well for: – Agentic AI workflows that require ongoing interaction – Long-running CLI sessions where context matters – Switching between desktop, laptop, and phone – Letting someone observe/debug without sharing SSH access It’s not about replacing SSH—it’s about making persistent, interactive workflows easier to manage. Install: npm install -g @chfischerx/puttry 👉 GitHub: https://lnkd.in/gdY44R4W 👉 Docs: https://puttry.io Would love feedback—especially how others handle persistent interactive sessions across devices. And if you find it useful, a star on GitHub is much appreciated.

PuTTrY

Web based terminal with multi session support

Web based terminal with multi session support