{"version":"2.1.280","anchor":"new-first-upload-bundling-path-for-teleporting-to-cloud-se","canonical_anchor":"new-first-upload-bundling-path-for-teleporting-to-cloud-se","heading":"New 'first upload' bundling path for teleporting to cloud sessions, plus a notice when repo settings try to control it","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-first-upload-bundling-path-for-teleporting-to-cloud-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New 'first upload' bundling path for teleporting to cloud sessions, plus a notice when repo settings try to control it\n\nTeleporting to a cloud session can now seed it from a 'first upload' instead of a full bundle, and repos can no longer control bundle seeding via committed settings\n\n**Unclear.** Whether the 'first upload' path actually makes teleporting faster or otherwise changes the user-visible experience beyond the outcome handling isn't stated.\n\n**What**\n\nStarting a cloud session (\"teleporting to remote\") now has a new fast path that can seed the new session from an initial \"first upload\" of files, before falling back to the older full bundle-and-clone process if needed. This includes a `created_empty` outcome for when the session starts with nothing to upload, with its own handling for that case.\n\nSeparately, if a repository's committed `.claude\/settings` files try to set keys related to bundle seeding, Claude Code now shows a notice that these are ignored. Bundle seeding is treated as a setting that belongs to the machine owner, not something a repository can control.\n\n**Why**\n\nThe new upload path is meant to make opening a cloud session faster in the common case. The settings notice prevents a shared repository configuration from silently overriding how a given machine seeds its own cloud sessions, and tells the user clearly when that's happening.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}