Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

set_permission_mode requests are queued, re-checked and report clearer errors

The SDK set_permission_mode request now re-checks auto mode when applied, can be queued or overtaken, and returns error codes such as invalid_mode

Group of 2 You'll notice Improvements
JSON All of v2.1.319
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SDKArea: what it touches
ImprovementsKind: in v2.1.319,
ImprovementsSection of the release

What

The SDK (the toolkit that lets other programs control Claude Code) can send a set_permission_mode request to change the permission mode, which decides how much Claude may do without asking you. This request has changed:

  • The auto-mode gate, the check on whether auto mode may be used, is now re-checked when the change is applied. Before, it was checked once, straight away, before the mode was set.
  • A request can be overtaken by a later one.
  • A request is queued, held to run in order, when a new check says it needs to be.
  • An unexpected failure returns the error "set_permission_mode failed".
  • A request with an invalid mode now gets an error that includes code: "invalid_mode". Before, there was no code field.

Why

Programs that change the permission mode several times in quick succession get the changes applied in a predictable order. A program can also check the invalid_mode code to tell a bad mode name apart from other failures.

See this entry in the whole of v2.1.319 →

Feedback