Note: Codespaces is currently in limited public beta and subject to change. For more information about joining the beta, see "About Codespaces."
In this guide, you'll create a codespace from the sample repository and explore some of the essential features available to you within the codespace.
The following example shows you how to create a codespace, connect to a forwarded port to view your running application, and personalize your setup with additional extensions and dotfiles.
Navigate to the main page of the sample repository.
Under the repository name, use the Code drop-down menu, and select Open with Codespaces.
To create a codespace, click New codespace.
With your project open in a codespace, you can now run the application and launch it in a browser.
Start the application by entering
npm run devin the terminal. This command executes the
devscript in the package.json file and starts up the web application defined in the sample repository.
When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
Click Open in Browser to view your running application in a new tab.
Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme but you can install any extension that is useful for your workflow.
In the left sidebar, click the Extensions icon.
In the search bar, enter
fairyflossand install the fairyfloss extension.
fairyflosstheme by selecting it from the list.
Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically to other codespaces via Settings Sync.
If your user account on GitHub owns a public repository named dotfiles, GitHub automatically uses this repository to personalize your codespace environment during codespace creation.
This example guides you through creating a dotfiles repository for your codespaces.
Navigate to the sample dotfiles repository.
Fork the repository to your account and ensure it's public.
Verify the repository created under your account is named dotfiles, for example
yourname/dotfiles. Any other name will cause Codespaces to ignore the repository for personalization.
Create a new codespace from the sample application repository as dotfile updates are only applied at creation time. The sample dotfiles will change the command prompt to bold purple and blue text.
You've successfully created, personalized, and run your first application within a codespace but there's so much more to explore! Here are some helpful resources for taking your next steps with Codespaces.