RunCloud Web Terminal is a collaborative, browser-based terminal built directly into the RunCloud dashboard. It allows eligible users to access a live shell on a RunCloud-managed server or web application without opening a separate SSH client. System Admin and Owner roles can start terminal sessions, while team members can join active sessions for real-time collaboration.
What is RunCloud Web Terminal?
RunCloud Web Terminal provides direct terminal shell access inside your browser. Whether you need to tail NGINX log files, restart system services, inspect running processes, execute database migrations, or run CLI commands (such as Laravel artisan, WP-CLI, or Composer), Web Terminal connects you instantly to your server environment.
In addition to single-user terminal access, Web Terminal supports real-time multiplayer collaboration: multiple team members can join the same active shell session, view real-time terminal output, and co-type commands together, turning troubleshooting and pair debugging from a solo copy-paste chore into a seamless team activity.
Web Terminal is built directly on RunCloud’s existing secure agent infrastructure. The browser connects via an encrypted WebSocket (wss://) through RunCloud’s stateless Nginx proxy directly to the internal agent port (34210). Server identity secrets and internal SSH keys are never exposed to the browser or stored in client-side storage.
Key Problems Solved
Traditional server management relies heavily on local terminal applications and SSH key orchestration. Web Terminal eliminates the friction associated with traditional SSH management:
- No Local SSH Client Required: Access your server shell from any device, including laptops, tablets, or mobile devices, without configuring local SSH software or terminal emulators.
- No SSH Setup for Web Terminal Access: Users can access supported terminal sessions through the RunCloud dashboard without configuring a local SSH client or SSH keys specifically for Web Terminal.
- Real-Time Collaborative Debugging: Collaborate live with team members inside the exact same terminal window. Eliminate the need to copy and paste command outputs or stack traces into team chat channels.
- Contextual Web Application Terminals: Open a terminal as the web application user and start directly in the application directory, without manually changing directories or switching users.
- Hardened In-Dashboard Access: Gain instant terminal access without exposing raw SSH server credentials or secret keys to the browser client.
Key Features
| Feature | Description |
|---|---|
| Server Enablement | Enabling Web Terminal requires owner verification using an 8-digit code sent to the server owner’s email address. The verification code is valid for 60 minutes. |
| Installation | Enabling Web Terminal does not install additional software on the server. The feature uses functionality already included in the supported RunCloud Agent. |
| Authentication Gate | A fresh 2FA challenge is required every time a user starts a terminal session. There is no “remember this browser” option for Web Terminal sessions, and users who have not enrolled in 2FA cannot use the feature. |
| Workspace Access Control | Only users with the System Admin or Owner role can start Web Terminal sessions. Other eligible team members can join an active session for collaboration. |
| Multiplayer Collaboration | Real-time co-typing in the same pseudo-terminal (PTY) shell with live collaborator notifications. |
| Floating Detached UI | Floating window overlay allows full dashboard navigation while maintaining an active terminal session. |
| Context Awareness | Server-level terminal launches as root; Web App-level terminal launches as the web application user in its root folder. |
| Server & Session Caps | Maximum 3 active sessions per server and maximum 10 collaborators per session. |
| Safety Watchdogs | Automatic teardown for dead connections (20s ping / 60s timeout), 10-minute idle inactivity (+60s warning), and a 4-hour absolute session age cap. |
Server and Web App Terminal Sessions
Web Terminal can be opened in two different contexts:
- Server terminal: Opens a server-level terminal session running as root.
- Web App terminal: Opens a terminal as the web application user and starts in that web application’s directory.
Use the server terminal when you need server-level access. Use the Web App terminal when working with files, commands, or tools related to a specific application.
Minimum Requirements & Compatibility
To use RunCloud Web Terminal, ensure your environment meets the following prerequisites:
- RunCloud Agent Version: The target server must run RunCloud Agent v2.19.0 or newer.
- Account 2FA Enrollment: Any user opening a terminal session must have Two-Factor Authentication (2FA) enabled on their RunCloud account.
- Role & Access Requirements:
- Only the Server Owner or Workspace Owner can enable or disable Web Terminal. Enabling the feature requires email verification.
- System Admin and Owner roles can start terminal sessions.
- Eligible team members can join an active terminal session for collaboration.
- Browser: Any modern web browser supporting WebSockets and HTML5 canvas/xterm.js rendering (Chrome, Firefox, Safari, Edge).