get codespace in Vscode?

[dsabSAB]

🏷️ Discussion Type

Question

Body

🏷️ Discussion Type
Question

Body

I'm starting to use GitHub Codespaces with Visual Studio Code, and I'm trying to understand how it works in practice.

How do I create and open a Codespace from VS Code, and what are the main benefits of using it instead of just setting up everything on my local machine?

[Haiagari]

Hi @dsabSAB,

Here is a step-by-step walkthrough for creating and opening a GitHub Codespace in VS Code (Desktop), along with the core practical advantages over a standard local setup.

---

Part 1: How to create and open a Codespace in VS Code Desktop

You can do this using either the desktop application directly or starting from the web:

Method A: Directly inside VS Code Desktop (Fastest)

1. Install the Extension: In VS Code, go to the Extensions view (Ctrl+Shift+X or Cmd+Shift+X) and install the official GitHub Codespaces extension.
2. Sign In: Click the Accounts icon in the bottom-left corner and sign in with your GitHub account.
3. Create the Codespace:
   • Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P).
   • Run: Codespaces: Create New Codespace...
   • Select your target repository, pick the branch, and select your preferred machine spec (e.g., 2-core / 4-core).
   • VS Code will connect securely to the remote container and mount your project files.

Method B: From the GitHub Web Interface

1. Navigate to your repository on github.com.
2. Click the green <> Code button and select the Codespaces tab.
3. Click the three dots (...) next to your Codespace (or create a new one) and choose "Open in Visual Studio Code".
4. Allow your browser to hand off the session to your local VS Code app.

---

Part 2: Key Benefits of Codespaces vs Local Setup

1. Deterministic Dev Environments (.devcontainer):
   • Eliminates the "it works on my machine" dilemma. Your runtime versions, system packages, database services, and recommended VS Code extensions can be declared in .devcontainer/devcontainer.json. Any collaborator gets an identical environment with zero manual setup.
2. Keeps Your Host Machine Clean:
   • You don't need to install conflicting SDK versions, global npm packages, or background services (PostgreSQL, Redis, etc.) directly on your personal computer. Everything lives strictly inside the disposable cloud container.
3. Offloaded Compute and Battery Savings:
   • Compilations, Docker builds, and test suites execute on high-performance cloud virtual machines rather than consuming your laptop's CPU, disk space, and battery.
4. Instant Task Switching:
   • You can test an open pull request or reproduce a bug on an isolated branch in a separate Codespace without stashing, switching branches, or altering your local working directory.
5. Generous Free Tier:
   • Every personal GitHub account gets 60 free core-hours per month on 2-core machines (or 30 hours on 4-core), making it very practical for personal projects and development workflows.

[dsabSAB]

thanks!!

[meruw]

GitHub Codespaces basically gives you a development environment in the cloud, so you don't have to set up everything from scratch on your own computer.

you can create or open a Codespace directly from vscode using the GitHub Codespaces extension. Once you're connected, it pretty much feels like you're working locally, except the actual environment is running in the cloud.

one of the nicest things about it is consistency. If the project uses something like a devcontainer.json file, everyone can have pretty much the same tools, dependencies, and setup. So you avoid the classic "it works on my machine" situation lol.

It's also really useful if you switch between computers, since you can just open the same Codespace and keep working without having to configure everything again.

[dsabSAB]

is it this one?

[meruw]

is it this one?

yes!