{"version":"2.1.283","anchor":"person-only-permission-prompts-skip-the-coordinators-automa","canonical_anchor":"person-only-permission-prompts-skip-the-coordinators-automa","heading":"Permission prompts marked person-only can now only be answered by a human","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/person-only-permission-prompts-skip-the-coordinators-automa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Permission prompts marked person-only can now only be answered by a human\n\nPermission asks marked personOnly now skip the classifier, hooks, the coordinator check and prompt-tool hook races, and guard against accidental keypresses\n\n**Unclear.** Whether the skipped check includes your own permission hooks or only the coordinator's own automation is not clear.\n\n**What**\n\nA permission ask is the prompt Claude Code shows before Claude does something that needs your approval. Some asks are now marked person-only (`personOnly`), meaning a person must answer them. One example is Claude reading someone else's artifact that was created outside your organization. For these asks:\n\n- The automatic resolver, the classifier that can approve actions on its own in auto mode, is no longer consulted.\n\n- Permission-request hooks (commands you configure to run automatically on certain events) are no longer run to answer the ask.\n\n- The coordinator's automated permission check is skipped. The ask carries `askIsPersonOnly` so that check can return early.\n\n- With `--permission-prompt-tool`, which hands permission prompts to an MCP tool in non-interactive mode, the hooks that normally race that tool are skipped, as they already were for remote execution. The ask must be answered by the prompt tool.\n\n- The internal `confirmWithUser` helper, built on AskUserQuestion, takes a new `personOnly` option. It sets `classifierApprovable` to false, so the classifier cannot answer the question.\n\n- The dialog opens with placement \"under\" and an input grace period, so keys you were typing just before it appeared do not answer it by accident.\n\n**Why**\n\nBefore, a hook, the classifier or the coordinator could settle a prompt that was meant for a person. Person-only prompts now always wait for a human, and are harder to approve by accident while typing.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}