UX Suggestion: Explicitly Label Conflicts as AI Blaze vs. TextBlaze

Quick proposal on the snippet conflict experience: could we make it more explicit when the conflict is coming from AI Blaze, not Text Blaze?

Right now, unless I click into the snippet from the Ignore/Proceed modal, it’s very hard to tell that the conflict isn’t within TextBlaze - it’s actually in AI Blaze.

A small icon would make the context immediately obvious and reduce misinterpretation (especially considering AI Blaze has some "out of the box" snippets with very common names).


Thanks for the feedback; that makes sense to me. It would help to make the conflict shortcut ("/reply" in your case) link to the prompt in AI Blaze, just like we already link to conflicting snippets in Text Blaze. We'll take a look at it.

1 Like