{"version":"2.1.299","anchor":"short-flag-normalisation-n-becomes-name","canonical_anchor":"short-flag-normalisation-n-becomes-name","heading":"Option values that start with a dash are now kept attached to their option","tier":"notice","area":"CLI","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/short-flag-normalisation-n-becomes-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Option values that start with a dash are now kept attached to their option\n\nWhen Claude Code passes options on, a value starting with a dash is joined with `=`, and `-n` is written out as `--name`\n\n**What**\n\nWhen Claude Code passes command-line options on to another process, it now rewrites certain short options whose value begins with a dash (`-`). The option and its value are joined with an equals sign, and `-n` is written out in its long form, `--name`. For example, `-n -draft` becomes `--name=-draft`.\n\n**Why**\n\nA value that begins with a dash can look like a separate option. Joining it to its option with `=` keeps it read as a value, so a session name such as `-draft` reaches the new process intact.\n\n- Area: CLI\n- Names: `--name`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}