Understand snapshots and rebuilds
Follow prepared environment versions and diagnose setup failures.
A snapshot is a prepared environment used as a starting point for sessions. It can include shared setup and repository hydration so a new session does not need to repeat every setup step from scratch.
Read the snapshot state
Open the workspace's seed snapshot or environment view. Inspect the current build, readiness, and build history. Follow a build to read its phases and errors.
A ready snapshot describes environment preparation. It does not prove that a particular agent turn started, a web server is running, or application tests passed.
Know what changed
Changes to attached repositories, active manifests, or required setup can make a new build necessary. A new revision can be preparing while an older environment still exists. Review the current build's source and configuration rather than inferring readiness from an earlier successful build.
Running sessions retain their own environment state. Editing a manifest does not retroactively rerun setup in every session.
Investigate a failed build
Identify the first failing phase and its command. For a checkout failure, inspect GitHub access. For dependency or setup errors, inspect the active manifest and supporting files. For credential errors, inspect the intended secret scope.
Use the rebuild or retry action offered by the page after correcting the cause. Repeating a build with unchanged invalid input usually repeats the same failure.
If a session is preparing slowly, compare its startup state with the workspace's build information. Keep the build and session links when asking for help. Follow startup recovery for work that was already accepted.