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.
What
Claude 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:
- picks different explanatory text depending on whether the container's position is
detachedorcurrent_branch - records the origin as
created_emptyin its internal facts, along with whether the container was rerouted
Why
This 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.
Names in the bundlecreated_empty
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what user-facing scenario produces a created_empty origin, or what text differs between the detached and…