Hot starts, batch inference, and what's next for Runpod Serverless. Webinar June 25.

VS Code Server on Runpod: Local-Quality Remote Development

Unlock seamless coding with the VS Code Server template on Runpod. Learn how to connect, code, and iterate remotely with local-like speed and responsiveness.

VS Code Server on Runpod: Local-Quality Remote Development

Experience a new level of development with Visual Studio Code (VS Code) and Runpod. This guide will walk you through using the VS Code Server template on Runpod, enabling you to leverage GPU instances for your development needs. By the end of this tutorial, you will be able to interact with your code directly from your locally installed VS Code.

Prerequisites

Before we start, ensure you have the following:

Step 1: Launch Your Development Server

Navigate to the Runpod interface and select the Runpod VS Code Server template. Click on "Deploy" to launch your development server. Once you've initiated the deployment, proceed to the "My Pods" section and wait for your pod to become ready.

VS Code Server Pod Template
VS Code Server Pod Template

Step 2: Access the Container Logs

Within the "My Pods" section, find your pod, select "Logs", and then select "Container Logs". This will give you access to the logs of your VS Code Server.

"My Pods" Page
"My Pods" Page

Step 3: Register Your VS Code Server

In your container logs, you will find a unique code for registering your VS Code Server. Copy this code, open a new window, and navigate to https://github.com/login/device. Paste the copied code into the provided field on this page. Before proceeding, ensure that there is a pause symbol in the lower right side of the log screen (not a play button). Click "Continue", authorize access, and your VS Code Server will be ready to use.

Runpod container logs with the code-server GitHub device login code highlighted and circled in red
GitHub Device Activation page with the eight-character device code entered
Container logs showing a VS Code tunnel being named and created on the pod

Step 4: Connect to the VS Code Server

Open VS Code on your local machine. In the "Remote Explorer" section, you should see an option to connect to the server. Follow the prompts to establish a connection to the VS Code Server running on your Runpod instance.

VS Code Remote Explorer showing the pod's tunnel listed as running

Congratulations! You are now directly connected to your Runpod instance using VS Code. Enjoy the familiar functionality of VS Code while also having the power to develop directly on a GPU-backed system!

VS Code connected to a Runpod pod, running a test.py script and nvidia-smi in the integrated terminal

Author profile: Justin Merrell

Related articles

View All
Deploy When Available is now GA

Deploy When Available is now GA

Queue for any GPU spec, even one that's fully rented out, and we'll deploy it the moment capacity opens up. No more refreshing the console or running a sniping tool.

All
The Chips Got Faster. The Stack Didn't.

The Chips Got Faster. The Stack Didn't.

Explore why faster chips have shifted the bottleneck to AI infrastructure, and what that means for teams running production workloads.

All

Build what’s next.

Build, train, and scale AI workloads on Runpod with cloud GPUs, Serverless, and Clusters.