{"version":"2.1.311","anchor":"personal-accepted-as-a-flag-ccr-disk-watchdog-log-now-con","canonical_anchor":"personal-accepted-as-a-flag-ccr-disk-watchdog-log-now-con","heading":"New --personal flag and persistentVolumeFromSessionId for cloud sessions","tier":"use","area":"CLI","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/personal-accepted-as-a-flag-ccr-disk-watchdog-log-now-con","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### New --personal flag and persistentVolumeFromSessionId for cloud sessions\n\nClaude Code recognizes a --personal flag, and session start-up and cloud session creation gain persistentVolumeFromSessionId\n\n**Unclear.** Which command accepts `--personal` and what it does are not stated.\n\n**What**\n\nSeveral pieces point to a new personal mode and to cloud sessions that can reuse storage from an earlier session:\n\n- `--personal` is now a recognized flag, listed next to `--allow-other-models` and `--unsandboxed`.\n\n- Interactive start-up takes `personal` and `persistentVolumeFromSessionId`. It can also add a `personalWithoutEffectNotification` to the notification queue.\n\n- Start-up now calls `primeCurrentRepository` instead of `detectCurrentRepositoryWithHost`.\n\n- Creating a cloud session now sends `persistentVolumeFromSessionId`, and retries creation after a bundle notice.\n\n- When you resume a session and a feature check passes, the session's team is re-keyed and its team context and teammate colours are updated.\n\n- The `ccr_disk_watchdog` log line is now written only when a new condition holds. Before, it was always written.\n\n**Why**\n\nThe members do not explain what `--personal` does. In practice it is a new start-up option, with a notification for the case where it has no effect. Resuming team sessions and creating cloud sessions also behave a little differently.\n\n- Area: CLI\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}