Codespaces idle timeout and resource consumption limits

GitHub Codespaces utilizes an automated idle timeout mechanism to stop virtual machines after a period of inactivity. This feature is designed to conserve compute hours and manage billing by suspending the environment when it is no longer in active use.

While the default idle timeout can be configured in the user settings to balance availability and cost, there is a tension between maintaining long-running background processes and avoiding the rapid exhaustion of monthly compute quotas. Because the suspension preserves the filesystem but not the volatile memory state, specific workloads may be interrupted unexpectedly.

• What are the specific triggers that GitHub defines as "activity" to prevent a timeout during long-running terminal operations?
• Is there a method to receive a notification alert before the idle timeout triggers a suspension?