{"version":"2.1.318","anchor":"ask-limit-policy-distinguishes-person-own-task-and-other-tr","canonical_anchor":"ask-limit-policy-distinguishes-person-own-task-and-other-tr","heading":"Ask limits now treat follow-ups to Claude's own tasks separately","tier":"internal","area":"Reply Gate","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/ask-limit-policy-distinguishes-person-own-task-and-other-tr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Ask limits now treat follow-ups to Claude's own tasks separately\n\nThe policy limiting how many asks are allowed now has a separate limit for asks after Claude's own task, alongside person and other triggers\n\n**Unclear.** It is unclear which feature this policy belongs to and whether it is active for users.\n\n**What**\n\nA policy caps how many asks are allowed after something happens. It used to choose between two limits: one after a person and one after a server event. It now picks between three cases:\n\n- `person` uses the limit for after a person\n\n- `own_task` uses a new limit for after Claude's own task, or the server-event limit if that is not set\n\n- `other` uses the server-event limit\n\n**Why**\n\nThis adds a separate knob for how many asks are allowed after Claude's own task finishes.\n\n- Area: Reply Gate\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}