diff --git a/docs/hpc/06_tools_and_software/09_vscode_remote_ssh_torch.mdx b/docs/hpc/06_tools_and_software/09_vscode_remote_ssh_torch.mdx
new file mode 100644
index 0000000000..ce6239e4a5
--- /dev/null
+++ b/docs/hpc/06_tools_and_software/09_vscode_remote_ssh_torch.mdx
@@ -0,0 +1,38 @@
+# Connect VSCode to Torch
+This page describes how to connect VSCode to the Torch login node. 
+
+## Step 1: Configure the Torch SSH Host
+
+Update your local `~/.ssh/config` to define a Torch SSH host for VSCode:
+
+```ssh-config
+Host torch
+  HostName login.torch.hpc.nyu.edu
+  User NetID
+  StrictHostKeyChecking no
+  UserKnownHostsFile /dev/null
+  LogLevel ERROR
+  ServerAliveInterval 60
+```
+
+Replace `NetID` with your NYU NetID.
+
+## Step 2: Connect
+Install the VSCode Remote - SSH extension. 
+
+Configure Remote - SSH settings:
+1. Check off `Remote.SSH: Lockfiles In Tmp`
+2. Uncheck `Remote.SSH: Use Flock`
+
+Because Torch requires Microsoft device authentication during SSH login, VSCode may time out before you finish entering the device code. If this happens, search for Remote.SSH: Connect Timeout and set it to 120.
+
+Before connecting, open https://microsoft.com/devicelogin and keep it ready. In VSCode Remote Explorer, connect to the Torch login node: torch. When VSCode prompts for Microsoft device authentication, enter the code on the device login page. This may take a few attempts. VSCode may also prompt more than once during setup because it can open multiple SSH connections.
+
+After authentication, VSCode may take a while to install or start the VSCode server on Torch. If the connection fails during this step, try connecting again. Once the server is installed successfully, future connections are usually more consistent.
+
+Once connected, open a terminal in the VSCode remote session. The prompt should show that you are on a Torch login node, for example:
+```bash
+[NetID@torch-login-... ~]$
+```
+
+
diff --git a/docs/hpc/06_tools_and_software/10_use_jupyter_notebooks_in_vscode_on_torch.mdx b/docs/hpc/06_tools_and_software/10_use_jupyter_notebooks_in_vscode_on_torch.mdx
new file mode 100644
index 0000000000..c88c5b79de
--- /dev/null
+++ b/docs/hpc/06_tools_and_software/10_use_jupyter_notebooks_in_vscode_on_torch.mdx
@@ -0,0 +1,54 @@
+# Use Apptainer Jupyter Notebooks in VSCode on Torch
+
+This page builds on the general VSCode access instructions in 09_vscode_remote_ssh_torch. Before following this workflow, complete that setup and connect VSCode to the Torch login node.
+
+## Step 1: Install VSCode Jupyter support
+
+After connecting VSCode to the Torch login node, open the Extensions view in the VSCode remote window and search for Jupyter.
+
+Install or enable the Microsoft Jupyter extension in the remote SSH environment. If the extension is not already installed remotely, VSCode should show an option such as:
+
+`Install in SSH: torch`
+
+## Step 2: Start a dummy batch job and connect to the compute node
+
+After the Jupyter extension is installed or enabled, open a terminal in the VSCode remote session on a Torch login node.
+
+Interactive jobs on Torch may experience intermittent issues. Some compute nodes may work as expected, while others may not. As a workaround, submit a lightweight dummy batch job and then ssh to the allocated compute node after the job is running.
+
+For example:
+
+```bash
+sbatch -c4 -t2:00:00 --mem=4G --account=<account_name> --wrap "sleep infinity"
+```
+
+Replace `<account_name>` with the account for your project. After submitting the job, Slurm will print a job ID, for example:
+
+```bash
+Submitted batch job <job_id>
+```
+
+Once the job is running, identify the assigned compute node and connect to it from the VSCode terminal using SSH.
+Check the job status and assigned node:
+```bash
+squeue -u $USER
+```
+
+```bash
+ssh csXXX
+```
+
+After connecting, the terminal prompt should show the compute node:
+```bash
+[NetID@csXXX ~]$
+```
+
+## Step 3: Open the notebook
+
+Open the target .ipynb notebook in VSCode.
+
+## Step 4: Select the Apptainer kernel
+
+Use the notebook kernel picker to select the Apptainer kernel for the notebook.
+
+If the Apptainer kernel does not appear, confirm that the kernel is installed and visible on Torch before retrying in VSCode.