Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

Plugin evidence resolution added (stack / resumed / dispatch)

New logic resolves which plugin is responsible for something via stack, resumed-session, or dispatch lookup

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

Unclear The finding doesn't say what feature relies on knowing which plugin is responsible, such as error reporting or telemetry.

What

A new function determines which plugin something belongs to by trying, in order: a stack-based lookup, a lookup for resumed sessions using an atomics-backed name table, and finally a dispatch-based lookup. Whichever method succeeds tags the result with an evidence field of "stack", "resumed", or "dispatch" noting how the answer was found.

Why

This makes plugin attribution more reliable across different situations, including sessions that have been resumed, and records how confident or by what method the attribution was made.

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 doubtThe finding doesn't say what feature relies on knowing which plugin is responsible, such as error reporting or telemetry.

See this entry in the whole of v2.1.280 →

Feedback