webterm
WebTerm is a persistent terminal application for your entire infrastructure, running in the browser. A signed agent dials out — nothing listens on your servers, so machines behind NAT just work. Sessions live in tmux and outlive every disconnect.
Ficha actualizada 22 sept 2026, 18:51 · upstream 22 sept 2026, 18:39 · release sin release detectada
Qué es webterm
Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.
Open a shell on any of your machines from a browser — including a phone — and come back to it hours later with the process still running and scrollback intact. Close the tab, restart the gateway, reboot your laptop: the session is on the host, in tmux, and waits for you.
Nothing listens on your servers. A small agent dials out over WebSocket to a single gateway container, so a machine behind NAT or on mobile works exactly like one with a public IP address. Sessions are stored persistently on the host filesystem via tmux, meaning they survive reboots of both client and server.
The gateway is a single Docker container that handles authentication (passkeys), 2FA, step-up policies for flagged hosts, audit logging, encrypted backups, and alerting. It never stores login credentials — only session tokens bound to the host IP address. This means you can revoke access without touching any passwords or secrets.
You can share sessions via a read-only or writable link with expiry, browse files on the host (including folders), expose services through port forwarding, reach devices behind your firewall via SSH or telnet bastion, and run fleets of hosts from a single command. All data is encrypted in transit and at rest.
- Maintain long-running jobs across multiple machines without losing state on reboot
- Connect to remote servers or IoT devices behind NAT/firewall with persistent sessions
- Share terminal sessions between team members via secure links for collaborative debugging
- Access serial console of embedded hardware from a browser on the office network
- Run fleet-wide deployments by executing commands across multiple hosts simultaneously
- Monitor and debug infrastructure components through a unified web interface
- Sessions persist in tmux on the host, surviving gateway restarts and client reboots without data loss
- Agent dials out over WebSocket with signed tokens — no credentials stored on servers or gateways
- Support for SSH, telnet bastion, serial console (RS232/485), port forwarding, file management, and fleet execution
- Command history is searchable via OSC 133 protocol; each command has identity metadata including exit code and duration
- File browser follows `cd` commands (OSC 7) with full directory navigation, rename, delete, and drag-and-drop upload of folders
- Telnet bastion allows CLI access to devices on the host's LAN without installing anything on the target machine
- Sessions are stored in tmux on each host — requires tmux installed on every connected machine
- Session history is limited to 32 sessions per host with a maximum of 2 MiB scrollback buffer per session
- File browser supports partial-read for large files but cannot fully browse or edit very large files
- Telnet bastion requires the target device to have telnet installed and may not work on modern devices without it
- Serial console support is limited to standard RS232/RS485/USB protocols — proprietary serial drivers are not supported
- The gateway acts as a single point of failure for authentication; if compromised, all session tokens become invalid
Perfil de infraestructura
Estimación inicial derivada del repositorio y de los servicios detectados.
Despliegue detectado
Qué señales reales de instalación hemos encontrado.
Deploy the gateway container on your server with `docker run -d --name webterm-gateway ...`. The agent is a single Python file that dials out over WebSocket. For fleet management, use the CLI to execute commands across hosts: `webterm fleet run <command> --host host1 --host host2`. Enable SSH or telnet bastion by configuring your gateway's IP address and adding the appropriate scheme (e.g., `telnet://<gateway-ip>:23`). Port forwarding is configured via a web UI on the gateway. For production, use HTTPS with TLS termination at the gateway level. Keep the agent running as a systemd service or cron job to ensure persistence across reboots.
Stack y dependencias
Componentes inferidos a partir de manifests, configuración y documentación.
Puede sustituir a
Relaciones detectadas por el análisis del repositorio y su categoría.
Experiencia real de la comunidad
Ayuda a contrastar la estimación automática con instalaciones reales.
Todavía no hay datos comunitarios para este proyecto.