{"version":"2.1.280","anchor":"linked-git-worktrees-can-now-be-uploaded-for-cloudteleport","canonical_anchor":"linked-git-worktrees-can-now-be-uploaded-for-cloudteleport","heading":"Linked git worktrees can now be uploaded for cloud\/teleport sessions","tier":"notice","area":"Git Worktrees","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/linked-git-worktrees-can-now-be-uploaded-for-cloudteleport","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Linked git worktrees can now be uploaded for cloud\/teleport sessions\n\nCloud\/teleport session uploads now support git linked worktrees\n\n**What**\n\nWhen Claude Code uploads a git bundle to seed a cloud or \"teleport\" session, it now explicitly handles linked git worktrees (a working directory checked out separately from the main repository copy). This includes:\n\n- correctly locating the private admin directory for a linked worktree\n\n- withholding credential files from the upload (`neverReadFor`)\n\n- recording new telemetry, including a `linked_worktree` field\n\n**Why**\n\nBefore this, starting a cloud or teleport session from a linked worktree likely didn't work correctly or safely; this makes that path explicit and keeps credentials out of the uploaded bundle.\n\n- Area: Git Worktrees\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}