Unclear Whether the 'first upload' path actually makes teleporting faster or otherwise changes the user-visible experience beyond the outcome handling isn't stated.
Starting 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.
Separately, 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.
The 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.
Whether the 'first upload' path actually makes teleporting faster or otherwise changes the user-visible experience beyond the outcome…