{"version":"2.1.280","anchor":"new-git-worktreesession-container-origin-kind-created-empt","canonical_anchor":"new-git-worktreesession-container-origin-kind-created-empt","heading":"New git-worktree\/session container origin kind: created_empty","tier":"internal","area":"Git Worktrees","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-git-worktreesession-container-origin-kind-created-empt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New git-worktree\/session container origin kind: created_empty\n\nClaude Code adds a created_empty origin kind for git worktree\/session containers\n\n**Unclear.** The finding does not say what user-facing scenario produces a created_empty origin, or what text differs between the detached and current_branch cases.\n\n**What**\n\nClaude Code's internal handling of where a session's container (a git worktree, the isolated working copy used for a session) comes from gains a new case called `created_empty`. When a container originates this way, Claude Code now:\n\n- picks different explanatory text depending on whether the container's position is `detached` or `current_branch`\n\n- records the origin as `created_empty` in its internal facts, along with whether the container was rerouted\n\n**Why**\n\nThis lets Claude Code correctly explain and track sessions whose worktree started out empty, rather than lumping them in with other origin kinds. Readers aren't likely to notice this directly, but it should make session\/worktree status messages more accurate in this specific case.\n\n- Area: Git Worktrees\n- Names: `created_empty`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}