{"version":"2.1.317","anchor":"macos-app-bundles-under-versionsbundles-are-now-locked-pro","canonical_anchor":"macos-app-bundles-under-versionsbundles-are-now-locked-pro","heading":"Updates no longer delete the macOS app a running session uses","tier":"notice","area":"Installation","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/macos-app-bundles-under-versionsbundles-are-now-locked-pro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Updates no longer delete the macOS app a running session uses\n\nA running Claude Code app bundle on macOS is now locked so updates skip it, and old bundles are cleaned up\n\n**What**\n\nOn macOS, Claude Code can run from an app bundle, a folder packaged as an application. When it runs this way, it now writes a lock file saying it is in use. Then:\n\n- Version cleanup leaves a locked bundle alone.\n\n- A new cleanup removes leftover unfinished or failed bundles and old bundles that are no longer in use.\n\n- Before cleaning, it checks the folder is yours and only you can write to it. If not, it refuses with a message.\n\nIf the lock file cannot be written, Claude Code warns that a later update may delete the bundle it runs from.\n\n**Why**\n\nAn update can no longer remove the app a running session depends on, and old bundles no longer pile up.\n\n- Area: Installation\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}