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.
