Connect a Desktop Editor with Remote SSH

A desktop editor with Remote SSH support can edit files directly on your TermSquad computer. First make sure a normal SSH connection works; then use the same hostname, Linux user, and key in the editor.

Before you connect

You need a running computer, a local SSH client, and an editor with a compatible remote-SSH feature or extension. Use the agent account for project work.

Add and test an SSH key using Connect with SSH. This separates connection problems from editor setup problems.

Example: Visual Studio Code

1. Install Microsoft’s Remote - SSH extension in VS Code.
2. Open the Command Palette and choose Remote-SSH: Connect to Host….
3. Enter agent@YOUR_HOSTNAME, replacing the hostname with the value from TermSquad Settings.
4. Complete authentication and choose Linux if asked for the remote platform.
5. Wait for the remote connection to initialize.
6. Open your project folder on the remote computer.

VS Code’s Remote SSH documentation explains local setup and connection options. Other editors have their own extension and platform requirements.

Check where you are working

Use the editor’s remote connection indicator. In its terminal, run whoami and pwd to check the account and folder. Saving a remote file changes the copy on TermSquad.

An editor’s new terminal does not automatically attach to a running browser agent. Use Herdr’s session list and attach command to return to existing persistent work.

If the editor cannot connect, test plain SSH again and follow SSH troubleshooting.