Gitpod Prebuild State Persistence for Interactive Setup

Gitpod Workspace Prebuilds utilize a snapshot mechanism to capture the filesystem state after .gitpod.yml tasks complete. This allows environments to launch with dependencies already installed, bypassing time-consuming initialization scripts.

A challenge arises when the environment setup requires a specific state that cannot be fully automated via non-interactive scripts, or when the filesystem snapshot must be conditionally applied based on external runtime variables not available during the prebuild phase.

Since runtime memory and active network connections are not captured in the snapshot, it is unclear how to handle dependencies that require a one-time interactive authentication or a dynamic token exchange during the prebuild process without stalling the automation.

• Can prebuild snapshots be configured to pause for external input without triggering a timeout?
• Is there a mechanism to inject runtime secrets into a prebuilt snapshot that preserves the filesystem state?