{"version":"2.1.281","anchor":"bash-path-checks-now-understand-cpmv-t-target-director","canonical_anchor":"bash-path-checks-now-understand-cpmv-t-target-director","heading":"Bash path checks now understand cp\/mv -t \/ --target-directory","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/bash-path-checks-now-understand-cpmv-t-target-director","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Bash path checks now understand cp\/mv -t \/ --target-directory\n\nBash permission checks now understand `cp` and `mv` with `-t` or `--target-directory` and check all their files as writes\n\n**What**\n\nBefore running a shell command, Claude Code checks whether the files it would write to are inside the folders you have allowed. The copy and move commands `cp` and `mv` can name their destination folder with an option instead of as the last argument. That option is now recognised in these forms:\n\n- `--target-directory`, including clear shortenings such as `--target`, and the `=value` form.\n\n- `-t`, including when it is combined with other single-letter options in one group.\n\nWhen a destination folder is given this way, every other file named in the command counts as a write. Before, only the last argument was treated as the destination. A destination attached directly to the option (`-t\/dir`, `--target-directory=dir`) is also added to the paths checked against your allowed folders.\n\n**Why**\n\nWith this form of `cp` or `mv`, the last argument is not the destination, so the old check looked at the wrong path. Now the real destination is the one checked against your allowed folders."}