{"version":"2.1.269","anchor":"artifact-auto-reply-can-hand-off-to-a-forkedsubagent-delive","canonical_anchor":"artifact-auto-reply-can-hand-off-to-a-forkedsubagent-delive","heading":"Artifact auto-reply can hand off to a forked\/subagent delivery path","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/artifact-auto-reply-can-hand-off-to-a-forkedsubagent-delive","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Artifact auto-reply can hand off to a forked\/subagent delivery path\n\nAuto-replies to artifacts can now be delivered through an alternate, forked\/subagent path\n\n**What**\n\nWhen Claude Code is about to send an automatic reply related to an artifact, it now checks a new condition and, if true, can route that reply through a new delivery path instead of the previous one. This new path can complete the delivery on its own, or hand off to a 'fork' (a separate branched task), in which case the older delivery code is skipped.\n\nThis is controlled by a gate called `tengu_sorrel_trellis_tenon`, which the flag server currently returns as off both for this site's account and for the general anonymous baseline.\n\n**Why**\n\nThis adds an alternate route for delivering auto-replies, potentially through a forked or subagent task, though it is not turned on for this site's account so it has no visible effect yet.\n\n- Flag `tengu_sorrel_trellis_tenon`: Off in both readings (read for one account on one subscription tier against v2.1.269; this account: off, anonymous baseline: off, compiled default: not a boolean we can read)\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}