Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.283 ·

Permission prompts marked person-only can now only be answered by a human

Permission asks marked personOnly now skip the classifier, hooks, the coordinator check and prompt-tool hook races, and guard against accidental keypresses

Group of 5 You'll notice Internal Changes
JSON All of v2.1.283
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Internal ChangesKind: in v2.1.283,
ImprovementsSection of the release

Unclear Which confirmations are marked person-only is not known.

What

A 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:

  • The automatic resolver, the classifier that can approve actions on its own in auto mode, is no longer consulted.
  • Permission-request hooks (commands you configure to run automatically on certain events) are no longer run to answer the ask.
  • The coordinator's automated permission check is skipped. The ask carries askIsPersonOnly so that check can return early.
  • 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.
  • The internal confirmWithUser helper, built on AskUserQuestion, takes a new personOnly option. It sets classifierApprovable to false, so the classifier cannot answer the question.
  • 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.

Why

Before, 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.

Read from
Names in the bundleAskUserQuestion
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on All settings touched a line naming AskUserQuestion after this was published. Let an unanswered [`AskUserQuestion`](/docs/en/tools-reference) dialog auto-continue after a period of idle time, submitting whatever options you had already selected. Set it when you step away and want Claude to continue without you. With… settings-reference see the edit
Confirmed since Anthropic's documentation has since written up AskUserQuestion, on Hooks reference. | `permissionDecision` | `"allow"` skips the permission prompt, except for the [actions no mode auto-approves](/docs/en/permission-modes#actions-no-mode-auto-approves) and for `AskUserQuestion` and `ExitPlanMode`, which need [`updatedInput… hooks see the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich confirmations are marked person-only is not known.
Anthropic's documentation agreesAnthropic's documentation has since written up AskUserQuestion, on Hooks reference.

See this entry in the whole of v2.1.283 →

Feedback