Using the Visual Studio Code Command Palette in GitHub Codespaces - GitHub Docs Skip to main content GitHub Docs Version: Free, Pro, & Team Search or ask Copilot Search or ask Copilot Select language: current language is English Search or ask Copilot Search or ask Copilot Open menu Collapse sidebar Expand sidebar Scroll breadcrumbs left * Home * Codespaces * Reference * VS Code Command Palette Scroll breadcrumbs right Codespaces * * * Quickstart * Getting started * What are Codespaces? * Codespaces features * The codespace lifecycle * Deep dive into Codespaces * Developing in a codespace * Develop in a codespace * Create a codespace for a repo * Create a codespace from a template * Delete a codespace * Open an existing codespace * Work collaboratively * Source control * Pull requests * Stop a codespace * Forward ports * Rebuilding a container * Default environment variables * Persist variables and files * Connecting to a private network * Machine learning * Visual Studio Code * GitHub CLI * Customizing your codespace * Rename a codespace * Change your shell * Change the machine type * Setting your user preferences * Personalize your codespaces * Set the default editor * Set the default region * Set the timeout * Configure automatic deletion * Choose the host image * Setting up your project * Adding a dev container configuration * Introduction to dev containers * Setting up a Node.js project * Setting up a C# (.NET) project * Setting up a Java project * Setting up a PHP project * Setting up a Python project * Configuring dev containers * Set a minimum machine spec * Adding features * Automatically opening files * Specifying recommended secrets * Setting up your repository * Facilitating codespace creation * Set up a template repo * Prebuilding your codespaces * About prebuilds * Configure prebuilds * Allow external repo access * Manage prebuilds * Test dev container changes * Managing your codespaces * Codespaces secrets * Repository access * Security logs * GPG verification * Managing your organization * Enable or disable Codespaces * Billing and ownership * List organization codespaces * Manage Codespaces costs * Manage secrets * Audit logs * Restrict machine types * Restrict codespace creation * Restrict base image * Restrict port visibility * Restrict timeout periods * Restrict the retention period * Reference * Access a private registry * Copilot in Codespaces * VS Code Command Palette * Security in Codespaces * Disaster recovery * Troubleshooting * Codespaces logs * Codespaces clients * Included usage * Exporting changes * Creation and deletion * Authenticating to repositories * Connection * Codespaces prebuilds * Personalization * Port forwarding * GPG verification * Working with support * github.dev editor Using the Visual Studio Code Command Palette in GitHub Codespaces You can use the Command Palette feature of Visual Studio Code to access many commands in GitHub Codespaces. Copy as Markdown In this article * About the Visual Studio Code Command Palette * Accessing the VS Code Command Palette * Commands for Codespaces * Further reading About the Visual Studio Code Command Palette The VS Code Command Palette is one of the focal features of Visual Studio Code and is available for you to use in GitHub Codespaces. The Command Palette allows you to access many commands for GitHub Codespaces and VS Code. For more information on using the VS Code Command Palette, see User Interface in the VS Code documentation. Accessing the VS Code Command Palette You can access the VS Code Command Palette in a number of ways. * Shift + Command + P (Mac) / Ctrl + Shift + P (Windows/Linux). Note that this command is a reserved keyboard shortcut in Firefox. * F1 * From the Application Menu, click View > Command Palette . Commands for Codespaces To see all commands related to GitHub Codespaces, access the VS Code Command Palette , then start typing "Codespaces". Suspending or stopping a codespace If you add a new secret or change the machine type, you'll have to stop and restart the codespace for it to apply your changes. To suspend or stop your codespace's container, access the VS Code Command Palette , then start typing "stop". Select Codespaces: Stop Current Codespace . Adding a predefined dev container configuration To add a predefined dev container configuration, access the VS Code Command Palette , then start typing "add dev". Click Codespaces: Add Dev Container Configuration Files . Rebuilding a codespace If you add a dev container or edit any of the configuration files ( devcontainer.json and Dockerfile ), you'll have to rebuild your codespace for it to apply your changes. To rebuild your container, access the VS Code Command Palette , then start typing "rebuild". Select Codespaces: Rebuild Container . Tip You may occasionally want to perform a full rebuild to clear your cache and rebuild your container with fresh images. For more information, see Rebuilding the container in a codespace . Codespaces logs You can use the VS Code Command Palette to access the codespace creation logs, or you can use it export all logs. To retrieve the logs for GitHub Codespaces, access the VS Code Command Palette , then start typing "export". Select Codespaces: Export Logs to export all logs related to GitHub Codespaces or select Codespaces: View Creation Logs to view logs related to the setup. Further reading * Using GitHub Codespaces in Visual Studio Code Back to top Help and support Was this Doc helpful? Yes No Help us make GitHub Docs great! All Docs are open source. See something that's wrong or unclear? Submit a pull request. Make a contribution Still need help? Provide GitHub Feedback Contact support Expert services Blog GitHub Inc. © 2026 Terms Privacy Status Pricing