{"version":"2.1.293","anchor":"safety-stop-count-field-on-results","canonical_anchor":"safety-stop-count-field-on-results","heading":"Session safety-stop count now documents what it counts and when it resets","tier":"internal","area":"Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/safety-stop-count-field-on-results","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Session safety-stop count now documents what it counts and when it resets\n\nThe result field counting safety stops covers refusals, content-filter stops and sometimes safety-monitor blocks, and resets on resume and \/clear\n\n**Unclear.** The name of this result field is not known.\n\n**What**\n\nResults include a count of how many times a safety system stopped one of the session's model calls. Its description now says it covers:\n\n- refusals by the model\n\n- content-filter stops\n\n- in some builds, blocks by a safety monitor\n\nThe count is never saved, so it starts again from zero when you resume a session or run `\/clear`.\n\n**Why**\n\nPrograms built on Claude Code can use this count to notice refusals, as long as they allow for it resetting.\n\n- Area: Agents\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}