{"version":"2.1.286","anchor":"permission-prompt-wording-access-change","canonical_anchor":"permission-prompt-wording-access-change","heading":"Access-change permission prompts reworded, default to No and need a person to answer","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/permission-prompt-wording-access-change","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Access-change permission prompts reworded, default to No and need a person to answer\n\nPrompts asking to change who can access something now say \"open or comment on\", default to No, and are marked person-only\n\n**What**\n\nA permission prompt is the question Claude Code asks before it takes an action that needs your approval. Actions that change who can reach something, such as sharing, are classed as `access_change`, and their prompt has changed.\n\n- The wording is now \"Allow Claude to change who can open or comment on\" instead of \"who can open or edit\".\n\n- The prompt now defaults to No (`defaultToNo`), as prompts for `delete` actions already did.\n\n- The prompt now carries `personOnly`, a new field marking it as one a person must answer.\n\n**Why**\n\nChanging who can see or comment on something is hard to undo. With No as the default, pressing Enter without reading declines the change. The person-only marking suggests these prompts are not meant to be approved automatically.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}