You'll notice
The /tui refusal message no longer calls out artifact-comment auto-replies as a separate case from other background work
What
When /tui (which sets the terminal UI renderer and relaunches) is refused because background work is running, it used to give a distinct message and telemetry label when the background work was specifically an artifact-comment monitor auto-replying to comments. That distinction is now gone: any active background work is reported the same way, with a single generic message telling you to wait or stop it via /tasks before running /tui again.
Why
This simplifies the refusal handling to one consistent message, at the cost of no longer telling you specifically that a comment monitor was the thing blocking the switch.
Names in the bundle/tui
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
Fixed /tui refusing to restart because of an agent-team teammate that had already finished its work and was no longer shown in the agents…