Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.275 ·

Artifact republish no longer re-asks when it's routine

← All of v2.1.275 Home All releases

Redeploying an Artifact that was already published routinely skips the confirmation prompt, tracked via routineRepublishedPaths

TierYou'll noticehow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaArtifactswhat it touches
KindImprovementsin v2.1.275,
Group of 2 You'll notice

Redeploying an Artifact that was already published routinely skips the confirmation prompt, tracked via routineRepublishedPaths

What

  • Publishing an Artifact now checks the Artifact's type-lock and capabilities before deciding whether to prompt for confirmation, and denies publishing a contract or type change once an Artifact is type-locked.
  • A new routineRepublishedPaths set and a routineUnasked flag track when a redeploy of the same path was already routine, so Claude Code doesn't ask for confirmation again for it.
  • This routineUnasked state is checked per path on frameUrls and is stamped onto both app state and the tool's returned data when it applies.

Why

This avoids repeatedly asking for confirmation when republishing an Artifact that's already been routinely republished, while still protecting against unexpected type changes on a locked Artifact.

See this entry in the whole of v2.1.275 →

Feedback