{"name":"perTaskStopAffordance","slug":"pertaskstopaffordance","family":"setting","title":"Settings keys","noun":"settings key","description":"SDK clients can opt in so an interrupt kills only the current turn, not background agents.","description_source":"entry","described_by":{"version":"2.1.246","anchor":"new-initialize-option-pertaskstopaffordance-changes-what-int"},"presence":{"first_seen":null,"removed_in":null,"in_current_build":false,"newest_mined":"2.1.308","builds":0,"mined_builds":149,"first_cited":{"version":"2.1.246","released_at":"2026-08-25 19:17:34","spans":1}},"aliases":[],"entries":[{"version":"2.1.271","anchor":"sdk-clients-can-now-declare-rapid-followup-preempt-support","heading":"SDK clients can now declare 'rapid followup preempt' support","line":"SDK clients can now declare support for preempting a running task on rapid follow-up input","released_at":"2026-09-14 19:45:19","reason":"found in this entry's text"},{"version":"2.1.246","anchor":"new-initialize-option-pertaskstopaffordance-changes-what-int","heading":"New initialize option perTaskStopAffordance changes what interrupt kills","line":"SDK clients can opt in so an interrupt kills only the current turn, not background agents.","released_at":"2026-08-25 19:17:34","reason":"named in this entry, found in this entry's text"},{"version":"2.1.246","anchor":"per-task-stop-is-first-attached-client-wins-and-does-not-sur","heading":"Per-task stop is first-attached-client-wins and does not survive a worker restart","line":"The first client to attach decides per-task stop behaviour, and it is lost on worker restart.","released_at":"2026-08-25 19:17:34","reason":"named in this entry, found in this entry's text"}],"entries_total":3,"docs":[],"docs_total":0,"gates":[],"related":[],"url":"https:\/\/changelogs.core-directive.com\/reference\/setting\/pertaskstopaffordance","family_url":"https:\/\/changelogs.core-directive.com\/reference\/setting.json"}