You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.233,
ImprovementsSection of the release
What
When a session started with --watch-artifact pulls an artifact with no user prompt behind it, having the artifact tool enabled is no longer enough on its own: matching deny or ask permission rules for that tool now block the read. Previously this path returned allowed outright.
Details
Only reached when the artifact read surface is enabled in the first place; prompt-driven reads are unchanged.
Evidence
promptless
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
