Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.284 ·

Plugins can cancel a model call cleanly

The plugin runtime's model.complete accepts an optional abort signal and returns an "aborted" result instead of throwing an error

Use it now Improvements
JSON All of v2.1.284
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.284,
What probably matters to youSection of the release
What

Plugins can ask Claude for an answer through a function called model.complete. That function can now take an optional abort signal, which is a way to tell a call to stop. If the signal fires before or during the call, the call does not throw an error. It returns a result that says the question was not answered, gives the reason as "aborted", and reports empty usage.

Why

Plugin authors can stop a model call part way through and handle that like any other outcome, without catching an error.

Read from
Names in the bundlemodel.complete
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.

Confirmed since Anthropic's documentation has since written up model.complete, on Claude Code changelog. * Added prompt caching to `$.model.complete` for mods: `prompt` and `system` take blocks of text, and `cache: true` on a block caches the request up to it changelog see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up model.complete, on Claude Code changelog.

See this entry in the whole of v2.1.284 →

Feedback