Claude Code Stops Misreporting Who Can Open a Published Artifact
Claude Code 2.1.328 fixes Claude calling an artifact private after reading one in a shared folder or publishing to another organization's, and saying only named people can open one when its folder's people can too. Claude is now told to check the artifact again instead of repeating the last publish's answer.
Key Takeaways
- Claude re-checks artifact visibility when asked.
- Shared folder artifacts are no longer called private.
- Cross-organization publishes are described correctly.
- Folder members are counted among who can open an artifact.
- Stale answers from the last publish are no longer repeated.
- Users get accurate sharing information.
Wrong Visibility Claims
Claude sometimes called an artifact private after reading one in a shared folder or publishing to another organization's, and said only named people could open it when its folder's people could too. These claims could mislead users about who could see their work.
The Fix
Claude is now told to check the artifact again when asked who can open it, instead of repeating the answer from the last publish. Visibility answers therefore reflect the current state.