{"version":"2.1.311","anchor":"cloud-worker-inherited-asks-settled-system-event-schema-adde","canonical_anchor":"cloud-worker-inherited-asks-settled-system-event-schema-adde","heading":"Cloud workers can report which open requests they took over","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/cloud-worker-inherited-asks-settled-system-event-schema-adde","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Cloud workers can report which open requests they took over\n\nAn internal message lets a cloud worker say, before its first turn, which open requests it kept from an earlier worker\n\n**What**\n\nA new internal system message, `inherited_asks_settled`, lets a Claude Code worker running in the cloud report, before its first turn, which open requests it inherited from an earlier worker and is keeping. Any earlier request it does not name is treated as over.\n\nTwo related checks were extended: a permission result check now knows about one-time answers only, and the API error check now recognises an unattended start limit.\n\n**Why**\n\nIt points to new handling when one cloud worker takes over from another.\n\n- Area: Cloud Sessions\n- Names: `inherited_asks_settled`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}