Ah, that's a straight out bug. Let me fix that quickly! To save time, some commands better handled locally get looked up on the client (we do that for a few re

Ah, that's a straight out bug. Let me fix that quickly! To save time, some commands better handled locally get looked up on the client (we do that for a few really common questions, commands etc). So it shouldn't even go to NLP intent detection. But if it does, it should identify it as a networking command intent and throw that back to the client. So it's double-stuffing-up here :) Thanks for catching that!