{"version":"2.1.217","anchor":"auto-mode-setup-gets-apply-target-request-id-and-expect-sha2","canonical_anchor":"auto-mode-setup-gets-apply-target-request-id-and-expect-sha2","heading":"\/auto-mode-setup Gets --apply-target , --request-id , and --expect-sha256","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.217\/e\/auto-mode-setup-gets-apply-target-request-id-and-expect-sha2","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.217","markdown":"### `\/auto-mode-setup` Gets `--apply-target`, `--request-id`, and `--expect-sha256`\n\nThe `\/auto-mode-setup` command now supports:\n\n- `--request-id <uuid>` \u2014 must come first; the UUID is echoed back in the JSON result as `requestId` so a host with multiple in-flight commands can match replies\n- `--apply-target <user|project>` \u2014 specifies where to save settings; the apply step validates that the proposal's scope matches the target (user \u2194 scope=all, project \u2194 scope=project)\n- `--expect-sha256 <64-hex>` \u2014 required before `--apply-file`; the apply refuses unless the file's bytes hash to the given SHA256\n\nThe proposal object returned by `--propose` now also includes the `scope` field.\n\n**Evidence**\n\nCommand usage string (search for `\"--apply-target must be\"`)"}