{"version":"2.1.265","anchor":"copy-from-asset-copy-tool-new-auto-approval-short-circuit-p","canonical_anchor":"copy-from-asset-copy-tool-new-auto-approval-short-circuit-p","heading":"copy_from asset-copy tool: new auto-approval short-circuit path","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/copy-from-asset-copy-tool-new-auto-approval-short-circuit-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### copy_from asset-copy tool: new auto-approval short-circuit path\n\nCopying assets between artifacts gains a new auto-approval path that can bypass the older consent check\n\n**Unclear.** The finding does not fully explain how this new branch interacts with the deny\/ask permission-rule engine described previously, so the exact practical effect on when a copy is allowed versus prompted is unclear.\n\n**What**\n\nWhen copying an asset from one artifact to another using `copy_from`, the permission flow now has an additional path: outside of plan-mode consent tracking, it can check a write-permission ruling from the automatic classifier and allow or ask for approval based on that, without going through the older consent-tracking flow for source and destination.\n\n**Why**\n\nThis is a further adjustment to how `copy_from` decides whether to allow, ask, or deny a copy, building on the permission-rule checks already added for this action; readers relying on that consent-based flow should be aware another path can now grant or request approval directly.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}