{"version":"2.1.323","anchor":"uploads-mounts-keyed-by-kind-rather-than-readonly","canonical_anchor":"uploads-mounts-keyed-by-kind-rather-than-readonly","heading":"Adding an uploads folder now checks the folder's kind, not read-only status","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/uploads-mounts-keyed-by-kind-rather-than-readonly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Adding an uploads folder now checks the folder's kind, not read-only status\n\nAdding a directory under \/uploads\/ now requires the folder to be an upload kind, rather than requiring it to be read-only\n\n**Unclear.** It is not clear whether any folder a user adds is now accepted or refused differently.\n\n**What**\n\nWhen a folder under `\/uploads\/` is added to a session, Claude Code checks the mount, the attached folder, before accepting it. It used to require the mount to be read-only. It now requires the mount to be of the \"upload\" kind. The path must still be under `\/uploads\/` and not under `\/uploads\/.home\/`.\n\n**Why**\n\nIt changes which attached folders are accepted when a directory is added.\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"}