{"version":"2.1.275","anchor":"env-var-snapshot-tracker-gains-explicit-snapshotsettled-stat","canonical_anchor":"env-var-snapshot-tracker-gains-explicit-snapshotsettled-stat","heading":"Env-var snapshot tracker gains explicit snapshotSettled state","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/env-var-snapshot-tracker-gains-explicit-snapshotsettled-stat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Env-var snapshot tracker gains explicit snapshotSettled state\n\nSandbox environment-variable snapshot tracking now separates 'settled' from 'available'\n\n**Unclear.** The finding does not say what practical behavior depends on distinguishing these two states.\n\n**What**\n\nThe internal component that tracks whether a snapshot of a sandbox or session's environment variables is ready now keeps track of two separate states: `snapshotSettled`, which becomes true once the snapshot process has finished running, and `snapshotAvailable`, which is a separate existing state. Resetting the tracker now clears both.\n\n**Why**\n\nThis distinguishes \"the snapshot process has finished\" from \"the snapshot succeeded and is usable,\" which is internal plumbing that helps Claude Code reason more precisely about the state of environment-variable snapshots.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}