{"version":"2.1.286","anchor":"new-worker-and-artifact-event-names-registered","canonical_anchor":"new-worker-and-artifact-event-names-registered","heading":"New artifact sharing flow, plus proxy refusal and cache keepalive names","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/new-worker-and-artifact-event-names-registered","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### New artifact sharing flow, plus proxy refusal and cache keepalive names\n\nCode for sharing artifacts with other people appears, with outcomes such as consent and person checks, plus proxy refusal and cache keepalive names\n\n**Unclear.** It is not known what the list is used for, so whether these features are live is unclear.\n\n**What**\n\nAn artifact is a piece of content Claude Code produces, such as a document. New code covers sharing artifacts with other people.\n\n- `artifact_share` is a new flow for reading and writing shared artifacts and working out which people they are shared with.\n\n- It has many possible outcomes, including `read_ok_foreign`, `write_relay_unapproved`, `consent_gone`, `not_person` and `people_unresolved`.\n\n- `ccr_worker_proxy_refusal` and `api_cache_keepalive` were added alongside it, pointing to handling for refused proxy requests from remote workers and to keeping a cache alive.\n\n- The memory rating writeback step no longer returns the values it cited.\n\n**Why**\n\nThis points to a new way to share artifacts with other people, with checks on consent, approval and whether a real person is involved. Nothing here shows that the feature is available to you yet.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}