SSH

The SSH applet lets you connect to remote servers directly from your project. Instead of opening a separate terminal app, looking up credentials, and typing ssh user@host every time, you save the connection once and open it in a tab. The session runs in the same GPU-accelerated terminal engine as the Terminal Session applet, so you get crisp text rendering and full shell functionality.

Every server, one click away

Managing servers is part of the job for most developers and teams. You check logs on staging, restart a service in production, run a migration on a database server. Each of those tasks usually means opening a terminal, remembering (or looking up) the hostname, finding the right SSH key, and connecting manually.

The SSH applet removes that friction:

• Saved connections per project. Store your staging server, production box, and CI runner as applets inside the project. One click to connect, no credentials to remember.
• Encrypted credential storage. Passwords and SSH keys are stored in an encrypted vault on your machine. They are never logged or stored in plain text.
• Test before you save. The connection form includes a Test Connection button that verifies your credentials before you commit to saving.
• Same terminal, different machine. The SSH terminal uses the same GPU-rendered engine as local terminal sessions. You get the same performance, the same font rendering, and the same keyboard behavior.
• Project context. Your server connections live alongside your code, docs, and deployments. When you need to check something on the server, you do not have to leave the workspace.

Adding an SSH Connection

To add an SSH connection, open the Add Applet dialog and select SSH under the Infrastructure category.

The creation form lets you configure:

• Name: a label for this connection (e.g. “Production Server”, “Staging DB”, “CI Runner”)
• Environment: tag for Production, Staging, or Development
• Host: the server hostname or IP address
• Port: defaults to 22
• Username: your server username

Authentication Methods

Choose one of three authentication methods:

• Password: enter the server password directly.
• SSH Key File: select a private key file from your local machine (e.g. ~/.ssh/id_rsa). If the key is encrypted, you can provide a passphrase.
• SSH Key Paste: paste the raw key content directly into the form. Useful when you do not have the key saved as a file. Also supports an optional passphrase for encrypted keys.

Click Test Connection to verify the credentials work before saving. A green “Connected” or red “Failed” badge shows the result.

Click Add SSH to save the connection. Credentials are stored in an encrypted vault and are never visible after saving.

Using an SSH Session

Open the SSH applet to start a terminal session on the remote server. The terminal connects automatically using the stored credentials.

The session works just like a local shell. You can run commands, navigate directories, use vim or nano, tail logs, run scripts, and do anything you would normally do over SSH. The connection info (username, host, and port) is shown at the top of the session.

If the remote connection ends or drops, the tab closes automatically. Reopen the SSH applet to start a new session.

Connection Settings

To update connection details after saving, open the SSH applet and switch to the Settings tab.

The settings page shows:

• Connection status: Connected, Failed, or Not Checked
• Test Connection: click to verify the current credentials
• Host and Port: update the server address
• Username: change the login user
• Authentication type: switch between Password, SSH Key File, and SSH Key Paste
• Credentials: update the password or key. Leave blank to keep the current value.
• Last checked: timestamp of the most recent connection test

Danger Zone

At the bottom of the settings page, you can remove the SSH applet from the project. This deletes the stored credentials and the applet record. A confirmation step prevents accidental deletion.

Widget

Appears when an SSH Terminal tab is active.

The widget panel shows:

• Connection configuration: hostname, username, port, and authentication type
• Connection status indicator (Connected / Failed / Not Checked)
• Check Now button to test the connection
• Error message display when the connection fails
• Last checked timestamp