Unclear what new resume feature this worktreeBranch/name validation is groundwork for
What
When 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.
Why
This 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.
Names in the bundleworktreeBranch
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up worktreeBranch, on Agent SDK reference - Python.
Returns the result from the subagent. The output is discriminated on the `status` field: `"completed"` for finished tasks, `"async_launched"` for background tasks, and `"remote_launched"` for tasks Claude Code dispatched to a cloud session…agent-sdk/python see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
what new resume feature this worktreeBranch/name validation is groundwork for
Anthropic's documentation agrees
Anthropic's documentation has since written up worktreeBranch, on Agent SDK reference - Python.