{"version":"2.1.319","anchor":"new-ccs-telemetrystage-names","canonical_anchor":"new-ccs-telemetrystage-names","heading":"Four new stage names for Claude Code's container setup","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/new-ccs-telemetrystage-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Four new stage names for Claude Code's container setup\n\nA list of stage names gains entries for a settings hold, its release, a container restart and an address guard\n\n**Unclear.** It is not clear what the list of stage names is used for, or whether these stages change anything a user sees.\n\n**What**\n\nA list of stage names inside Claude Code gains four new entries:\n\n- `ccs_settings_hold`\n\n- `ccs_settings_hold_let_go`\n\n- `ccs_container_restart_by_ccr`\n\n- `ccs_address_guard`\n\n**Why**\n\nThe names point to work on holding settings and guarding addresses in the containers Claude Code runs in. Nothing else in this release shows what the list does.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}