The Terminal page lets you connect to SSH servers from your browser. You save connection details once and then launch sessions with a single click. Each session runs in a full terminal emulator inside the page.Documentation Index
Fetch the complete documentation index at: https://hyperspeed.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
SSH connections
SSH connections are stored at the workspace level and are available to all spaces in that workspace. To manage them, open any space’s Terminal page and click Settings.Creating a connection
Open settings
Click Settings in the Terminal page header. The settings panel lists your existing connections and a form to add a new one.
Fill in the connection details
Provide:
- Name — a label to identify the connection (for example, “Production server”)
- Host — the hostname or IP address of the server
- Port — the SSH port (default is
22) - Username — the user to log in as
Choose an authentication method
Select either Private key or Password:
- Private key — paste your private key (and optional passphrase) into the fields provided. The key is stored encrypted.
- Password — you can store the password, or leave it blank and enter it each time you connect.
Deleting a connection
In the settings panel, click Delete next to the connection you want to remove. If you have an active session using that connection, it will be disconnected.Launching a terminal session
Connect
Click Connect. The terminal initialises and establishes an SSH session with the server. A status indicator in the header shows whether the session is connecting, connected, or in an error state.
Use the terminal
Type commands as you would in any terminal. The terminal supports colour output, scrollback, and automatic resize when you change the window size.
If your connection uses password authentication and you did not store a password, a prompt appears when you connect. Enter the password there — it is sent directly to the server and is not saved.
Credential security
Stored SSH credentials (private keys and passwords) are encrypted at rest using an encryption key configured by your workspace administrator (HS_SSH_ENCRYPTION_KEY). The credentials are never exposed in the browser after they are saved.