Where to find it: in the Hub (your MSP workspace at app.theonestack.com), open RMM, then use the RMM sidebar or page links below:
- RMM → Devices → All Devices (open a device, then Terminal): app.theonestack.com/rmm/devices
- RMM → Devices → Terminal History: app.theonestack.com/rmm/terminal-history
Overview
Remote Terminal gives technicians a browser-based command-line shell into any online enrolled device. No VPN, no third-party tool — the session runs through the RMM agent already on the device.
Opening a Remote Terminal Session
- Open RMM and navigate to Devices.
- Click the device you want to connect to. The device must show an Online status.
- Click Remote Terminal.
- A terminal window opens in the browser. Within a few seconds the shell prompt from the remote device appears. You are now running commands directly on that machine.
On Windows, the shell is PowerShell or Command Prompt depending on agent configuration. On macOS and Linux, the shell is Bash.
Running Commands
Type commands exactly as you would in a local terminal. Standard navigation, file operations, and administrative commands all work. Output appears in real time.
If you need to run a saved script rather than typing commands manually, use Remote Commands or Automation Scripts instead.
Credential Injection
If you need to authenticate as a different user or paste a password during the session, use Inject Credential rather than typing the password by hand.
- Click Inject Credential in the terminal toolbar.
- Select the credential entry from your CMDB password vault.
- Click Confirm.
The agent types the username and password into the active window on the device. The staged credential is encrypted end-to-end and expires automatically after 60 seconds whether or not it is used. Your clipboard is never involved.
Session Security
- Sessions require your RMM login. Only users with technician or admin access can open a terminal.
- The connection is relayed through the RMM service over an encrypted WebSocket. The terminal stream never travels through your local machine as plaintext.
- All terminal sessions are recorded. Recordings are accessible from Terminal Recordings in the RMM menu if you need to review what was done in a session.
- Sessions that remain idle for five minutes are closed automatically by the server.
Ending a Session
Close the terminal tab or browser window to end the session. You can also type exit in the shell. Idle sessions close on their own after five minutes.
Frequently Asked Questions
The terminal connects but disconnects a few seconds later.
This is usually a brief network interruption on your side. Close the tab and reopen the terminal. If the problem persists for one specific device, check that device's CPU usage and agent health on the device detail page.
Credential injection typed the wrong thing or nothing happened.
The staged credential expires after 60 seconds. Click Inject again to stage a fresh one. Make sure the CMDB entry has both a username and a password saved.
Can two technicians have a terminal open to the same device at once?
Yes. Each technician gets an independent session. Presence indicators on the device page show who else is currently viewing or connected to the device.
Is there a way to see what was done in a past terminal session?
Yes. Go to Terminal Recordings in the RMM navigation. Sessions are indexed by device and timestamp.