{"version":"2.1.315","anchor":"artifact-docs-create-wake-behind-tengu-breezy-acorn-default","canonical_anchor":"artifact-docs-create-wake-behind-tengu-breezy-acorn-default","heading":"Creating a document with the artifact tool in a remote session can set a wake","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/artifact-docs-create-wake-behind-tengu-breezy-acorn-default","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Creating a document with the artifact tool in a remote session can set a wake\n\nIn remote sessions, successfully creating a document with the artifact tool can now set a wake, when artifacts and comments are both on\n\n**Unclear.** It is not clear what setting a wake does after a document is created.\n\n**What**\n\nIn remote sessions, where `CLAUDE_CODE_REMOTE` is set, Claude Code now watches the artifact tool. When a document is created successfully and the result holds a valid slug, a short name identifying the document, Claude Code tries to set a wake.\n\nIt skips this and records the reason when any of these is off:\n\n- the remote setting that controls the feature, which is on unless it is switched off remotely\n\n- the artifact tool\n\n- comments\n\n**Why**\n\nBecause the controlling setting falls back to on, this may already happen in remote sessions that have artifacts and comments on.\n\n- Flag `tengu_breezy_acorn`: Not enough to say (read for one account on one subscription tier against v2.1.315; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Artifacts\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}