{"version":"2.1.295","anchor":"cloud-home-seed-settings-upload-handles-broken-or-symlinked","canonical_anchor":"cloud-home-seed-settings-upload-handles-broken-or-symlinked","heading":"Settings sent to a cloud session are checked for broken or linked files first","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/cloud-home-seed-settings-upload-handles-broken-or-symlinked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Settings sent to a cloud session are checked for broken or linked files first\n\nBefore copying your settings to a cloud session, Claude Code now checks whether the settings file is broken or is a shortcut to another file\n\n**What**\n\nWhen Claude Code copies your personal settings into a cloud session (a session that runs on a remote machine rather than your own computer), it now inspects your user settings file first. The file is treated as broken if it contains an error or if it is a symlink, which is a file that only points to another file somewhere else.\n\nWhen a settings file cannot be safely checked, Claude Code records one of two causes:\n\n- `too_many_links`: the file passes through too many links to follow\n\n- `alias_unreadable`: the file the link points to cannot be read\n\nWhen some of your settings are refused, the message you see now refers to \"the rest of your settings\" being sent. The message shown when the copy runs out of time has also been reworded.\n\n**Why**\n\nCopying settings into cloud sessions is now more careful about invalid or linked settings files, so a damaged or redirected file is caught instead of being sent as it is.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}