> For the complete documentation index, see [llms.txt](https://igb.mit.edu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://igb.mit.edu/mini-courses/research-computing-on-engaging-with-vscode/vscode/connecting-to-engaging.md).

# Connecting to Engaging

After configuring your SSH keys by following the [SSH Configuration](/mini-courses/research-computing-on-engaging-with-vscode/vscode/ssh-configuration.md) page and installing both VSCode and the **Remote-SSH extension** you can login to Engaging by following the commands below.

1. Open the VSCode command palette.
   1. Windows: **Ctrl + Shift + P**
   2. MacOS: **Command + Shift + P**
2. Search for the **Remote-SSH: Connect to Host** option, and click it.

<figure><img src="https://498238201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWuHhstIreJ3jFvE4gQ3y%2Fuploads%2FuQBSroWbJIOUE323O4z4%2FScreenshot%202026-08-17%20at%201.39.14%20PM.png?alt=media&amp;token=ce2cdb6a-e705-4d1c-960f-67a88bb57e08" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
To directly login to an Engaging compute node on **Windows**, you must manually start a compute node session from the Engaging head node, then edit your SSH configuration file with the compute node you were granted. For example:

```bash
[asoberan@login008 ~]$ salloc --time=2:00:00
# salloc: Pending job allocation 23556187
# salloc: job 23556187 queued and waiting for resources
# salloc: job 23556187 has been allocated resources
# salloc: Granted job allocation 23556187
# salloc: Nodes node3603 are ready for job
[asoberan@node3603 ~]$ 
```

The SSH configuration file is located at `C:\Users\<your local username>\.ssh\config` . Change `HostName` to `node3603`.

```ssh-config
Host orcd-login
    HostName orcd-login.mit.edu 
    User asoberan
    IdentityFile C:\Users\asoberan\.ssh\orcd
    IdentitiesOnly yes

Host orcd-compute
  User asoberan
  HostName node3603
  ProxyJump orcd-login
```

{% endhint %}

3. Select the configured Engaging host:
   1. **orcd-login**: To login to the Engaging login node.
   2. **orcd-compute**: To login to an Engaging compute node.
4. A new window will open with a VSCode session connected to Engaging.

<figure><img src="https://498238201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWuHhstIreJ3jFvE4gQ3y%2Fuploads%2FgWgudhVQtPxFiLlQQylW%2FScreenshot%202026-08-17%20at%201.40.39%20PM.png?alt=media&amp;token=4850b14c-c6e7-4aae-90f1-b56bfc5a2460" alt=""><figcaption></figcaption></figure>

All actions performed in this remotely-connected window will be executed on Engaging. For example, if you click the left-hand sidebar menu option **Explorer > Open Folder**, you can open a remote folder. Doing this will populate your explorer with your Engaging files and directories, and opening a terminal via **Terminal > New Terminal** will start a shell on Engaging.

<figure><img src="https://498238201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWuHhstIreJ3jFvE4gQ3y%2Fuploads%2FEWgO3BliPTGyedCbh1PS%2FScreenshot%202026-08-17%20at%201.43.35%20PM.png?alt=media&amp;token=ca856c1f-93f5-4aee-befa-7c13b385b5ce" alt=""><figcaption></figcaption></figure>

Likewise, you can navigate to the **Ports** menu to forward a local port on your computer to a port on the Engaging cluster. We will see an example of this in a later section.