Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release
What
When the permission mode (such as switching to 'default' or 'acceptEdits') changes, Claude Code now keeps track of whether that change came from you answering a permission prompt or from elsewhere, such as a remote worker.
When a permission-request response sets the session-scoped mode to default or acceptEdits, the UI now calls a new noteOwnPermissionModeAnswer callback, alongside a parallel noteOwnPermissionModePush, so the outer session layer can attribute the change to answering a permission dialog.
In Remote Control's transport layer, the permission-mode change handler now takes an origin argument distinguishing a mode set by the person from one set by the worker, and the same noteOwnPermissionModePush/noteOwnPermissionModeAnswer methods track locally-initiated mode changes through a modeWire structure.
Why
This prevents the interface from mistakenly echoing back a permission-mode change as if it came from somewhere else when it was really something you just did yourself, particularly during remote/worker sessions.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed writes through a symlinked path being judged by their in-tree spelling: the prompt names where the write lands, and acceptEdits, allow…
