{"meta":{"title":"Using the Visual Studio Code Command Palette in GitHub Codespaces","intro":"You can use the Command Palette feature of Visual Studio Code to access many commands in GitHub Codespaces.","product":"Codespaces","breadcrumbs":[{"href":"/en/codespaces","title":"Codespaces"},{"href":"/en/codespaces/reference","title":"Reference"},{"href":"/en/codespaces/reference/using-the-vs-code-command-palette-in-codespaces","title":"VS Code Command Palette"}],"documentType":"article"},"body":"# Using the Visual Studio Code Command Palette in GitHub Codespaces\n\nYou can use the Command Palette feature of Visual Studio Code to access many commands in GitHub Codespaces.\n\n## About the Visual Studio Code Command Palette\n\nThe 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](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette) in the VS Code documentation.\n\n## Accessing the VS Code Command Palette\n\nYou can access the VS Code Command Palette in a number of ways.\n\n* Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux).\n\n Note that this command is a reserved keyboard shortcut in Firefox.\n* F1\n* From the Application Menu, click **View > Command Palette**.\n\n## Commands for Codespaces\n\nTo see all commands related to GitHub Codespaces, [access the VS Code Command Palette](#accessing-the-vs-code-command-palette), then start typing \"Codespaces\".\n\n\n\n### Suspending or stopping a codespace\n\nIf 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.\n\nTo suspend or stop your codespace's container, [access the VS Code Command Palette](#accessing-the-vs-code-command-palette), then start typing \"stop\". Select **Codespaces: Stop Current Codespace**.\n\n\n\n### Adding a predefined dev container configuration\n\nTo add a predefined dev container configuration, [access the VS Code Command Palette](#accessing-the-vs-code-command-palette), then start typing \"add dev\". Click **Codespaces: Add Dev Container Configuration Files**.\n\n\n\n### Rebuilding a codespace\n\nIf 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.\n\nTo rebuild your container, [access the VS Code Command Palette](#accessing-the-vs-code-command-palette), then start typing \"rebuild\". Select **Codespaces: Rebuild Container**.\n\n\n\n> \\[!TIP]\n> 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](/en/codespaces/developing-in-codespaces/rebuilding-the-container-in-a-codespace#about-rebuilding-a-container).\n\n### Codespaces logs\n\nYou can use the VS Code Command Palette to access the codespace creation logs, or you can use it export all logs.\n\nTo retrieve the logs for GitHub Codespaces, [access the VS Code Command Palette](#accessing-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.\n\n\n\n## Further reading\n\n* [Using GitHub Codespaces in Visual Studio Code](/en/codespaces/developing-in-a-codespace/using-github-codespaces-in-visual-studio-code)"}