Ajshen at 03:36, 29 June 2026

2026-06-29T03:36:35Z

← Older revision		Revision as of 03:36, 29 June 2026
Line 1:		Line 1:

			[[Category:IDEs]]
			[[Category:Remote Server Access]]
			[[Category:Department Servers]]
			[[Category:Wright Cluster]]
			[[Category:PSC]]

	Using '''VS Code Remote Development''', you can edit files, run visual breakpoint debuggers, and execute terminals directly on the remote server—while keeping the smooth, graphical interface of your local laptop.		Using '''VS Code Remote Development''', you can edit files, run visual breakpoint debuggers, and execute terminals directly on the remote server—while keeping the smooth, graphical interface of your local laptop.

Ajshen: Created page with " Using '''VS Code Remote Development''', you can edit files, run visual breakpoint debuggers, and execute terminals directly on the remote server—while keeping the smooth, g..."

2026-06-26T05:11:53Z

Created page with " Using '''VS Code Remote Development''', you can edit files, run visual breakpoint debuggers, and execute terminals directly on the remote server—while keeping the smooth, g..."

New page

Using '''VS Code Remote Development''', you can edit files, run visual breakpoint debuggers, and execute terminals directly on the remote server—while keeping the smooth, graphical interface of your local laptop.

This page covers the two primary workflows for connecting VS Code to the department and university servers.

<div style="background-color: #fff3cd; border-left: 5px solid #ffc107; padding: 15px; margin-bottom: 20px; margin-top: 15px; overflow: hidden;">
'''Important: Choosing the Right Workflow'''<br>
The method you use depends entirely on the server's architecture. <br>
* '''Workflow 1''' is only for the Department Servers (Leviathans/Ghidorahs) which do not use a job scheduler. <br>
* '''Workflow 2''' is required for larger shared clusters (like Wright or PSC) that use the Slurm job scheduler. Never run VS Code directly on a Slurm login node!
</div>

== 1. Department Servers (Remote - SSH) ==
For department servers without Slurm scheduling, you can use the official Remote - SSH plugin to connect directly to the machine. This effectively starts a VS Code server instance on the Leviathan or Ghidorah node and links it to your local application.

<div style="background-color: #f8f9fa; border-left: 4px solid #005A9C; padding: 15px; margin-bottom: 10px;">
'''Step-by-Step Setup:'''<br>
1. '''Install the Extension:''' Open your local VS Code. Go to the Extensions tab (<code>Ctrl+Shift+X</code> or <code>Cmd+Shift+X</code>) and search for '''Remote - SSH''' (published by Microsoft). Install it.<br>
2. '''Open the Command Palette:''' Press <code>F1</code> or <code>Ctrl+Shift+P</code> (Windows/Linux) / <code>Cmd+Shift+P</code> (Mac).<br>
3. '''Initialize Connection:''' Type <code>Remote-SSH: Connect to Host...</code> and press Enter. Select '''+ Add New SSH Host...'''<br>
4. '''Enter SSH Command:''' Type your SSH connection string. For the department servers, this will look like:<br>
<code>ssh [userid]@leviathan1.stat.cmu.edu</code><br>
5. '''Connect & Authenticate:''' Select your SSH configuration file to save the host. A new VS Code window will open. If prompted, select '''Linux''' as the target operating system. Enter your password when prompted.<br>
6. '''Open Folder:''' Click the "Open Folder" button in the Explorer pane to open your specific research directory on the server.
<br><br>
🔗 '''[https://www.youtube.com/watch?v=CDjqhAN5RqA Video Tutorial: Connect VS Code to Remote Servers via SSH]'''<br>
''For a visual walkthrough of installing the extension, setting up the host, and navigating the Remote Explorer panel.''
</div>

== 2. Slurm Clusters (Remote Tunnels) ==
For massive clusters like Wright or PSC, you cannot simply SSH and start coding. The login node (the machine you first connect to) is strictly for submitting jobs; running heavy VS Code server processes there will drain resources and likely get your account suspended.

Instead, you must request a compute node using Slurm, launch a VS Code Tunnel on that specific node, and connect to it locally. '''Note: This guide assumes the <code>code</code> CLI is already installed on the cluster.'''

<div style="background-color: #f8f9fa; border-left: 4px solid #dc3545; padding: 15px; margin-bottom: 10px;">
'''Step-by-Step Setup:'''<br>
1. '''SSH into the Login Node:''' Open your standard terminal and SSH into the cluster.<br>
2. '''Request an Interactive Compute Node:''' Use <code>srun</code> to request an interactive session with the resources you need. For example, to request 4 CPUs and 16GB of RAM for 2 hours:<br>
<code>srun --job-name vscode --time=2:00:00 --mem-per-cpu=48GB --partition=statds --ntasks=1 --gres=gpu:1 --cpus-per-task=2 --pty code tunnel
</code><br>
3. '''Authenticate the Tunnel:''' The terminal will output a secure link and an authentication code (usually linking to a GitHub or Microsoft account). Open this link in your local web browser and enter the provided code to link the session.<br>
4. '''Connect to the Node:''' The terminal will then provide a '''vscode.dev/tunnel/...''' URL. Open this URL in your local browser to access the full VS Code interface running directly on your allocated compute node.<br>
5. '''Alternative (Local App):''' If you prefer the desktop app over the browser, you can install the '''Remote - Tunnels''' extension in your local VS Code, sign in with the same account, and connect to the active tunnel listed in your Remote Explorer panel.
</div>

VS Code Remote - Revision history

Ajshen at 03:36, 29 June 2026

Ajshen: Created page with " Using '''VS Code Remote Development''', you can edit files, run visual breakpoint debuggers, and execute terminals directly on the remote server—while keeping the smooth, g..."