{"version":"2.1.269","anchor":"agent-resume-gains-worktreebranch-and-name-validation-ground","canonical_anchor":"agent-resume-gains-worktreebranch-and-name-validation-ground","heading":"Agent resume gains worktreeBranch and name validation groundwork","tier":"internal","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/agent-resume-gains-worktreebranch-and-name-validation-ground","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Agent resume gains worktreeBranch and name validation groundwork\n\nResuming an agent now validates its worktree branch and name before proceeding\n\n**Unclear.** what new resume feature this worktreeBranch\/name validation is groundwork for\n\n**What**\n\nWhen resuming an agent, Claude Code now computes and validates a `worktreeBranch` value (checking it's a string via a helper function) and a `name` value (checked against a naming pattern plus an exclusion list) from the resume options, alongside the existing handling of `toolUseId` and `description`.\n\n**Why**\n\nThis adds validation groundwork around resuming agents into a specific worktree (an isolated git working copy) and name, though the finding doesn't say what feature this validation will support.\n\n- Area: Subagents\n- Names: `worktreeBranch`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}