Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.219 ·

live-edit refused on workshop pages

Live-edit would be blocked on workshop pages so changes go through the validating publish path.

Nothing to try yet In Development
JSON All of v2.1.219
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.219,
In DevelopmentSection of the release

Workshop live-edit refusals are wired with detection and messages but sit behind the same gate, off by default.

What

The Artifact tool blocks live-edit actions against workshop pages so edits go through the publish path that validates them.

Details
  • Target slug is checked against the session's known workshop slugs, then open frame URLs, then a server-side fetch looking for a ws-decisions island.
  • A match refuses with workshop_live_edit_refused; a transient read failure refuses with workshop_live_edit_unverifiable and tells you to retry or WebFetch the page.
  • Same gate as the verifier: Xde() / tengu_gable_onyx_sluice, fallback off.
Evidence

live-edit is not available on workshop pages \u2014 edit the local workshop file and republish; the publish path is the validation chokepoint live-edit would bypass

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_gable_onyx_sluice Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.219: off

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.

Read once, for one account on one subscription tier, against v2.1.219. It isn't a statement about your account. What a flag value here can and cannot tell you

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_gable_onyx_sluice

See this entry in the whole of v2.1.219 →

Feedback