{"meta":{"title":"Deleting a codespace","intro":"You can delete a codespace you no longer need.","product":"Codespaces","breadcrumbs":[{"href":"/en/codespaces","title":"Codespaces"},{"href":"/en/codespaces/developing-in-a-codespace","title":"Developing in a codespace"},{"href":"/en/codespaces/developing-in-a-codespace/deleting-a-codespace","title":"Delete a codespace"}],"documentType":"article"},"body":"# Deleting a codespace\n\nYou can delete a codespace you no longer need.\n\n## Overview\n\nGitHub Codespaces are automatically deleted after they have been stopped and have remained inactive for a defined number of days. The retention period for each codespace is set when the codespace is created and does not change. The default retention period is 30 days. See [Configuring automatic deletion of your codespaces](/en/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces?tool=webui).\n\nYou can manually delete a codespace in a variety of ways:\n\n* In the terminal by using GitHub CLI\n* In Visual Studio Code\n* In your web browser\n\nUse the tabs at the top of this article to display instructions for each of these ways of deleting a codespace.\n\n> \\[!NOTE]\n> You can't delete a codespace from within JupyterLab.\n\n## Why you should delete unused codespaces\n\nThere are costs associated with storing codespaces. You should therefore delete any codespaces you no longer need. See [GitHub Codespaces billing](/en/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces).\n\nThere are limits to the number of codespaces you can create, and the number of codespaces you can run at the same time. These limits vary based on a number of factors. If you reach the maximum number of codespaces and try to create another, a message is displayed telling you that you must remove an existing codespace before you can create a new one.\n\n## Deleting a codespace\n\n\n\n> \\[!NOTE]\n> You may have prebuild codespaces that are consuming additional storage which are not displayed on this dashboard. To delete them, follow the steps for “[Deleting a prebuild configuration](/en/codespaces/prebuilding-your-codespaces/managing-prebuilds#deleting-a-prebuild-configuration).”\n\n\n\nYou can delete codespaces from within VS Code when you are not currently working in a codespace.\n\n1. In VS Code, in the Activity Bar, click the Remote Explorer icon.\n\n \n\n > \\[!NOTE]\n > If the Remote Explorer is not displayed in the Activity Bar:\n >\n > 1. Access the Command Palette. For example, by pressing Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux).\n > 2. Type: `details`.\n > 3. Click **Codespaces: Details**.\n2. Under \"GitHub Codespaces,\" right-click the codespace you want to delete.\n3. Click **Delete Codespace**.\n\n
\n\n\n\n> \\[!NOTE]\n> To learn more about GitHub CLI, see [About GitHub CLI](/en/github-cli/github-cli/about-github-cli).\n\nTo delete a codespace use the `gh codespace delete` subcommand and then choose a codespace from the list that's displayed.\n\n```shell\ngh codespace delete\n```\n\nIf you have unsaved changes, you'll be prompted to confirm deletion. You can use the `--force` flag to force deletion, avoiding this prompt.\n\nFor more information about this command, see [the GitHub CLI manual](https://cli.github.com/manual/gh_codespace_delete).\n\n
\n\n## Bulk deleting codespaces\n\n\n\nYou can use GitHub CLI to delete several or all of your codespaces with a single command. For more information, click the \"GitHub CLI\" tab near the top of this page.\n\n
\n\n\n\nYou can use GitHub CLI to delete several or all of your codespaces with a single command. For more information, click the \"GitHub CLI\" tab near the top of this page.\n\n
\n\n\n\nYou can delete several or all of your codespaces with a single command, using `gh codespace delete` followed by one of these flags:\n\n`--all` - Delete all of your codespaces.\n\n`--repo REPOSITORY` - Delete all of your codespaces for this repository. Or use together with the `--days` flag to filter by age of the codespace.\n\n`--days NUMBER` - Delete all of your codespaces that are older than the specified number of days. Can be used together with the `--repo` flag.\n\nBy default you are prompted to confirm deletion of any codespaces that contain unsaved changes. You can use the `--force` flag to skip this confirmation.\n\n### Example\n\nDelete all of the codespaces for the `octo-org/octo-repo` repository that you created more than 7 days ago.\n\n```shell\ngh codespace delete --repo octo-org/octo-repo --days 7\n```\n\n
\n\n## Deleting codespaces in your organization\n\nAs an organization owner, you can use GitHub CLI to delete any codespace in your organization.\n\n\n\nFor more information, click the \"GitHub CLI\" tab near the top of this page.\n\n
\n\n\n\nFor more information, click the \"GitHub CLI\" tab near the top of this page.\n\n
\n\n\n\n1. Enter one of these commands to display a list of codespaces.\n * `gh codespace delete --org ORGANIZATION` - Lists the current codespaces in the specified organization.\n * `gh codespace delete --org ORGANIZATION --user USER` - Lists only those codespaces created by the specified user.\n You must be an owner of the specified organization.\n2. In the list of codespaces, navigate to the codespace you want to delete.\n3. To delete the selected codespace press Enter.\n\n If the codespace contains unsaved changes you will be prompted to confirm deletion.\n\n
\n\nYou can also use the REST API to delete codespaces for your organization. See [REST API endpoints for Codespaces organizations](/en/rest/codespaces/organizations#delete-a-codespace-from-the-organization).\n\n## Further reading\n\n* [Understanding the codespace lifecycle](/en/codespaces/about-codespaces/understanding-the-codespace-lifecycle)\n* [Configuring automatic deletion of your codespaces](/en/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces)\n* [Restricting the retention period for codespaces](/en/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)"}