{"version":"2.1.273","anchor":"new-telemetry-pair-for-artifact-publish-permission-asks-cal","canonical_anchor":"new-telemetry-pair-for-artifact-publish-permission-asks-cal","heading":"New telemetry pair for artifact publish permission asks, caller not confirmed","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-telemetry-pair-for-artifact-publish-permission-asks-cal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New telemetry pair for artifact publish permission asks, caller not confirmed\n\nClaude Code now logs telemetry when it asks for, and receives, permission to publish an artifact\n\n**Unclear.** Whether this logging is enabled for any accounts is unknown, since both related gates are unread.\n\n**What**\n\nClaude Code now logs a `tengu_artifact_ask` event whenever it asks for permission to perform an artifact-publish-style action, and a `tengu_artifact_ask_granted` event when that permission is approved. The granted event also records how it was approved: by the user temporarily, by the user permanently, by a hook (an automated script that runs on certain events), by configuration, or by another method.\n\n**Why**\n\nThis telemetry helps track how often artifact publishing requires explicit permission and how users typically respond, without changing what the user sees or has to do.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}