{"version":"2.1.284","anchor":"plugin-modelcomplete-becomes-abort-aware","canonical_anchor":"plugin-modelcomplete-becomes-abort-aware","heading":"Plugins can cancel a model call cleanly","tier":"use","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/plugin-modelcomplete-becomes-abort-aware","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Plugins can cancel a model call cleanly\n\nThe plugin runtime's model.complete accepts an optional abort signal and returns an \"aborted\" result instead of throwing an error\n\n**What**\n\nPlugins 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.\n\n**Why**\n\nPlugin authors can stop a model call part way through and handle that like any other outcome, without catching an error.\n\n- Area: Plugins\n- Names: `model.complete`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}