When auto-reply to artifact comments stands down, Claude now tells you once why instead of staying silent.
Auto-reply suppression notices exist behind the artifact auto-react gate, which is off by default.
What's wrong with this entry?
Instead of silently doing nothing, the scanner posts a one-time in-session notice per artifact explaining why auto-reply is suppressed.
- covers plan mode, the hourly cap being reached, and a permission mode that only allows notification
- also covers repeated denials from a permission hook or content gate, which pauses affected threads until a successful auto-reply elsewhere on the same artifact
- behind the auto-react gate
auto-reply is paused while in plan mode; use the Artifact tool to read and reply.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.