Follow Discord
Sweep 09 Oct 2026 · 17:27Z Build v2.1.296 517 read Stable v2.1.287 Latest v2.1.296 Next v2.1.296 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.296 ·

Bad permission updates from connected apps now go through shared handling

Malformed updatedPermissions replies from a bridge client are now handled by a shared routine labelled as refusing them

Under the hood Internal Changes
JSON All of v2.1.296
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Internal ChangesKind: in v2.1.296,
Internal ChangesSection of the release

Unclear Whether malformed permission updates from a bridge client are still simply ignored or are now refused in a way the app sees is not stated.

What

When another app connected to a session through the bridge answers a permission question, its reply can include updatedPermissions, a set of permission changes. A malformed set used to be dropped with the warning "Malformed updatedPermissions from bridge client ignored". It now goes through a shared routine, labelled "refused" and "bridge client". The same routine also handles permission replies that arrive for a question no longer waiting.

Why

Malformed permission updates from connected apps are now dealt with in one place. The warning text you see in logs is different.

Read from
Names in the bundleupdatedPermissions
What the documentation says
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 doubtWhether malformed permission updates from a bridge client are still simply ignored or are now refused in a way the app sees is not stated.

See this entry in the whole of v2.1.296 →

Feedback