{"version":"2.1.269","anchor":"resuming-an-in-process-teammate-now-validates-its-recorded-n","canonical_anchor":"resuming-an-in-process-teammate-now-validates-its-recorded-n","heading":"Resuming an in-process teammate now validates its recorded name more strictly","tier":"notice","area":"Team Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/resuming-an-in-process-teammate-now-validates-its-recorded-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Resuming an in-process teammate now validates its recorded name more strictly\n\nResuming an in-process teammate now rejects a wider range of malformed recorded names\n\n**What**\n\nWhen Claude Code resumes an in-process teammate (a subagent running in the same process), it now checks the teammate's recorded name more strictly: the name must be a non-empty string matching a specific pattern and must not look like an agent ID. Previously this check only screened out reserved names. Names that fail now produce a clearer error explaining the name is reserved, looks like an agent ID, or isn't a valid name.\n\n**Why**\n\nThis prevents resuming a teammate with a malformed or ambiguous name, catching more bad cases than before and giving a clearer error when it happens.\n\n- Area: Team Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}