Your first connection
From installation to a verified terminal session. Start with one server you already have permission to access.
Before you start
- Use ShellMate 3.3.0 and select the intended account or workspace.
- Confirm the host/provider access and permissions required by this guide.
Let’s walk through it.
- 01
Install ShellMate
Open Download and choose the package for your operating system and CPU architecture. Install and launch the desktop app.
- 02
Sign in and set up your key
Sign in to your account and follow the device enrollment and key setup prompts. Keep your ShellMate Key (.smk) and recovery material somewhere safe. Your account password and your vault key serve different purposes.
- 03
Add a host
Open Hosts and choose Add Host. Enter a friendly name, address, SSH port and remote username. Select the appropriate authentication method and save.
- 04
Connect
Choose Connect on the host. Complete any authentication prompt. ShellMate verifies a remote response before marking a supported connection successful.
- 05
Explore the workspace
Use the terminal tab for commands and the host tools for available file, service and diagnostic workflows. Close the session when finished.
What success looks like
A verified remote SSH session opens for the intended host. Supported discovery updates the host’s saved OS observation.
Good to know.
Before you begin
You need an account, a reachable SSH server and valid remote credentials. For a team host, you also need host access and permission to start sessions. AWS access is an alternative workflow, not a prerequisite for SSH.
Desktop and browser
The desktop app opens remote terminals and decrypts your vault locally. My Page in the browser manages account information, host metadata, activity, team access and supported integrations. It is not a browser SSH terminal.
Worked example: a development server
Suppose your administrator gives you dev.example.com, SSH port 22, username deploy and an SSH private key. In Add Host, use Development API as the name, dev.example.com as the address, 22 as the port and deploy as the identity username. Select the matching private-key credential in Vault. These are example values: replace them with your own server details.
First-connection checklist
Before connecting, confirm the server address and remote username. Review any host identity prompt against a fingerprint obtained through a trusted channel. If authentication requests a key passphrase or password, enter it in the app’s authentication flow. Do not paste credentials into the shell as commands.
Confirm success
A supported connection should leave the pending state after remote verification and present the remote shell. Check the host name in the tab before running a harmless command such as pwd. A host card can update its observed OS details after discovery; that observation does not guarantee future uptime.
End your first session
When you finish, disconnect the remote terminal. Logging out of ShellMate and closing a terminal are different actions; inspect active sessions in the relevant view if you need to confirm which connections remain open.
A few common questions.
Why is my host still connecting?
Authentication may still be waiting for input, or the remote startup command may have failed. Check the terminal prompt and error message. A locally started SSH process alone does not prove a remote connection.
Can I reset my vault with my account password?
An account password reset does not recover encrypted vault contents. Use the supported .smk/key recovery flow and keep your recovery material private.
A key works in another SSH client but not here
Compare the username, port, selected key and key passphrase, and check whether the other client uses a jump host or SSH agent. Use the same approved connection path rather than changing the server’s authentication configuration blindly.