{"version":"2.1.273","anchor":"tui-switch-refusal-message-drops-the-artifact-comment-monito","canonical_anchor":"tui-switch-refusal-message-drops-the-artifact-comment-monito","heading":"TUI-switch refusal message drops the artifact-comment-monitor case","tier":"notice","area":"UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/tui-switch-refusal-message-drops-the-artifact-comment-monito","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### TUI-switch refusal message drops the artifact-comment-monitor case\n\nThe \/tui refusal message no longer calls out artifact-comment auto-replies as a separate case from other background work\n\n**What**\n\nWhen `\/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.\n\n**Why**\n\nThis 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.\n\n- Area: UI\n- Names: `\/tui`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}