Does GitHub Codespaces' automatic shutdown timeout reset when a CPU-intensive background process is actively running?

GitHub Codespaces includes an automatic shutdown timeout designed to power down environments after a period of inactivity. The default timeout is 30 minutes of no user activity. A documented behavioral detail specifies that this timer does not reset when a CPU-intensive background process is actively running, which may result in premature shutdown of the codespace despite ongoing computational work. This behavior interacts with persistent volume retention, where data survives shutdowns, and with organization-level admin policies that can override individual user settings for automatic shutdown enforcement.

The precise goal is to understand whether the shutdown timer's inactivity detection is solely based on user-facing idle time, or if it also accounts for background process activity, and how this affects long-running data processing workflows within codespaces. Uncertainty remains regarding the interaction between devcontainer.json shutdown_timeout configuration, organization-wide policy overrides, and the persistence of cached datasets across unexpected terminations.

Does the automatic shutdown timeout consider sustained CPU or I/O activity from background processes as user activity? Can organization-level shutdown policies be configured to preserve codespace uptime for long-running computational jobs without disabling the feature entirely? Which mechanisms, if any, allow a background process to signal activity to prevent premature timeout while maintaining security and cost controls?