{"version":"2.1.299","anchor":"artifact-tools-mod-sharing-prompt-text-and-resume-denied","canonical_anchor":"artifact-tools-mod-sharing-prompt-text-and-resume-denied","heading":"Mod authors get new guidance on how to share what they build","tier":"notice","area":"Mods","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/artifact-tools-mod-sharing-prompt-text-and-resume-denied","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Mod authors get new guidance on how to share what they build\n\nClaude Code now suggests publishing a mod to your organization's library when it can, and otherwise a GitHub repository, public or private\n\n**Unclear.** Which conditions turn this sharing guidance on is not stated beyond an organization setting being involved.\n\n**What**\n\nWhen you build a mod with Claude Code's artifact tools, Claude Code now gives the model instructions on how to help you share it:\n\n- If the publishing tool is available, it offers to publish the mod to your organization's library.\n\n- Otherwise it offers to put the mod in a GitHub repository, and asks you directly whether it should be public or private.\n\nSeparately, when an editing session for an artifact tries to resume and is refused, Claude Code now records that refusal.\n\n**Why**\n\nThe sharing advice you get depends on what your setup allows, and you are asked outright before anything goes public.\n\n- Area: Mods\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}