{"version":"2.1.265","anchor":"new-artifact-summon-forecast-preview-when-claude-is-busy","canonical_anchor":"new-artifact-summon-forecast-preview-when-claude-is-busy","heading":"New 'artifact summon forecast' preview when Claude is busy","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-artifact-summon-forecast-preview-when-claude-is-busy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New 'artifact summon forecast' preview when Claude is busy\n\nClaude now previews whether it would be allowed to auto-reply to a new artifact comment while it's still busy\n\n**Unclear.** The gate `tengu_madrone_spindle_newel` controlling this is unread for this release, so whether it is enabled here is unknown.\n\n**What**\n\nWhen a new comment or summon arrives on an artifact (a generated document or piece of content) while Claude is still busy handling something else, Claude Code now runs a quick permission-only check to forecast whether its eventual automatic reply would actually be allowed. It then posts an early status, either 'working' or a decline, instead of waiting until the busy work finishes to find out the reply was going to be blocked.\n\n**Why**\n\nThis gives earlier, more accurate feedback about pending artifact replies instead of leaving the requester waiting only to learn later that permission would have been denied.\n\n- Flag `tengu_madrone_spindle_newel`: Not enough to say (read for one account on one subscription tier against v2.1.265; this account: no value returned, anonymous baseline: off, compiled default: not a boolean we can read)\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}