{"version":"2.1.229","anchor":"artifact-summon-status-is-reported-back-to-the-server","canonical_anchor":"artifact-summon-status-is-reported-back-to-the-server","heading":"Artifact summon status is reported back to the server","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/artifact-summon-status-is-reported-back-to-the-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Artifact summon status is reported back to the server\n\nClaude Code reports artifact summon status back to the artifact host with a short timeout.\n\n**What**\n\nNew code posts a status update, reason, gesture timestamp, a per-artifact session id and a sequence number to a summon-status endpoint on the artifact host, with a 5 second timeout.\n\n**Details**\n\n- The session id is derived by HMAC per artifact slug, and updates are sequenced.\n- Emits `artifact_summon_status_emit` telemetry for success, skip and failure, with reasons route_absent, no_auth, http_failed and request_error.\n- A 404 from the endpoint backs the whole reporter off for a cooldown window.\n\n**Evidence**\n\n`artifact_summon_status_emit`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}