{"version":"2.1.310","anchor":"artifact-watching-changes-under-a-gate-cl","canonical_anchor":"artifact-watching-changes-under-a-gate-cl","heading":"New wording for artifact watching and separate prompts for database reads and edits","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/artifact-watching-changes-under-a-gate-cl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### New wording for artifact watching and separate prompts for database reads and edits\n\nUnder a new condition, --watch-artifact uses new notice text and the Artifacts tool asks separately for database reads and edits\n\n**Unclear.** What condition switches this new watching mode on is not stated.\n\n**What**\n\nThe `--watch-artifact` flag (an option you add when starting Claude Code) has Claude follow an artifact for changes. When a new condition is met, the watch notice now reads \"Watching artifact for new versions and comments you send to Claude.\" instead of the previous message about keeping track of new versions. Claude is also told about a comment only when you send it one of the artifact's comments.\n\nThe permission prompt for the Artifacts tool, which is where you approve or refuse an action, now has:\n\n- Separate versions for reading and editing a database\n\n- Edit prompts that the automatic approval check cannot approve, so you are always asked yourself\n\n**Why**\n\nArtifact watching behaves differently in this mode, and edits through the Artifacts tool always wait for your approval.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}