{"version":"2.1.280","anchor":"cloudremote-sessions-teleport-can-now-seed-from-a-first","canonical_anchor":"cloudremote-sessions-teleport-can-now-seed-from-a-first","heading":"Cloud\/remote sessions (teleport) can now seed from a 'first upload' of the local checkout when there's no git remote","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/cloudremote-sessions-teleport-can-now-seed-from-a-first","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Cloud\/remote sessions (teleport) can now seed from a 'first upload' of the local checkout when there's no git remote\n\nRemote sessions can now seed from a first upload of your local files when there's no git remote\n\n**What**\n\nWhen starting a cloud or remote session (teleport) for a project that has no GitHub remote and no bundle, Claude Code can now seed the session from a 'first upload' of your local working directory instead. The created session records this as its source, and Claude Code now tracks how many bytes were uploaded, how long it took, and whether the upload was 'detached' (not tied to a specific commit).\n\n- The 'no repository detected' warning now only appears if there is neither a bundle nor this first-upload path available.\n\n**Why**\n\nThis lets remote sessions start from your actual local files even when there's no git remote to sync from, instead of just warning that no repository was found.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}