{"version":"2.1.269","anchor":"subagent-forks-can-now-request-a-custom-display-name-and-des","canonical_anchor":"subagent-forks-can-now-request-a-custom-display-name-and-des","heading":"Subagent forks can now request a custom display name and description","tier":"soon","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/subagent-forks-can-now-request-a-custom-display-name-and-des","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Subagent forks can now request a custom display name and description\n\nSubagents spawned as forks can now be given a custom display name and description instead of one derived from the task text\n\n**What**\n\nWhen Claude Code launches a subagent as a 'fork' internally, the launch function now accepts optional `nameHint` and `description` fields. If provided, these override the agent's allocated name and its shown description, which were previously always derived automatically from the raw task prompt text.\n\n**Why**\n\nThis allows subagents to be labeled more clearly and meaningfully than an auto-generated name or truncated prompt snippet, making it easier to tell forked subagents apart when several are running.\n\n- Area: Subagents\n- Names: `nameHint`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5"}