A codespace will stop running after a period of inactivity. You can specify the length of this timeout period. The updated setting will apply to any newly created codespace.
Some organizations may have a maximum idle timeout policy. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting, and you will be notified of this after the codespace is created. For more information, see "Restricting the idle timeout period."
Warning: Codespaces are billed per minute. If you are not actively using a codespace but the codespace has not yet timed out, you are still billed for the time that the codespace is running. For more information, see "About billing for Codespaces."
In the "Code, planning, and automation" section of the sidebar, click Codespaces.
Under "Default idle timeout", enter the time that you want, then click Save. The time must be between 5 minutes and 240 minutes (4 hours).
To learn more about GitHub CLI, see "About GitHub CLI."
To set the timeout period when you create a codespace, use the
idle-timeout argument with the
codespace create subcommand. Specify the time in minutes, followed by
m. The time must be between 5 minutes and 240 minutes (4 hours).
gh codespace create --idle-timeout 90m
If you don't specify a timeout period when you create a codespace, then the default timeout period will be used. For information about setting a default timeout period, click the "Web browser" tab on this page. You can't currently specify a default timeout period through GitHub CLI.