This article explains how billing works for your codespaces, and explains how your organization's billing manager can help.
Your organization's administrator might limit GitHub Codespaces usage to only specific personal accounts. To get access, you will need to contact your billing manager. For more information, see "Managing access and security for your codespaces."
To see the pricing for Codespaces usage, see "Codespaces pricing."
Your codespace is billed for its compute minutes and for the amount of storage it uses on disk.
If you enable prebuilding of codespaces this will incur additional charges. For more information, see "About GitHub Codespaces prebuilds."
Your codespace is billed for the number of minutes that it's active. If your codespaces window is left idle for 30 minutes, it will automatically shutdown, and compute billing for the codespace will end until you start the codespace again.
For GitHub Codespaces, storage is defined to include any files relating to your codespace, such as the cloned repository, configuration files, and extensions, among others. This storage is billed while your codespace is shutdown. The storage billing for a codespace ends when you manually delete it from https://github.com/codespaces.
Before your organization can use Codespaces, your billing manager will need to set a spending limit. For more information, see "Managing spending limits for GitHub Codespaces."
If you hit a spending limit, you will no longer be able to create or resume your codespaces. You can still export any work in progress changes to a new branch.
If you need to check your current usage or spending limit, contact your organization's billing manager. For more information, see "Viewing your GitHub Codespaces usage."
Your codespace will be automatically deleted when you are removed from an organization or repository.
You can manually delete your codespaces in https://github.com/codespaces and from within Visual Studio Code. To reduce the size of a codespace, you can manually delete files using the terminal or from within Visual Studio Code.