I get that stuff is going to change as the product evolves. But there are different kinds of changes, including "improvements", "downgrades", and "arbitrary changes for no good reason", to name a few.
What we're seeing now falls squarely in the "arbitrary changes for no good reason" class - right now I get different results from the same keystrokes depending on the day. I'm not arguing against introducing AI to your platform - I'm arguing against breaking an existing interface to generate some new behaviour when the interface has an established pattern of use, and there are other ways of accomplishing the task. And I'm especially against having the interface change back and forth arbitrarily from day to day - this is needlessly frustrating. Why would you think this is a good idea?
Suggestion
I get that stuff is going to change as the product evolves. But there are different kinds of changes, including "improvements", "downgrades", and "arbitrary changes for no good reason", to name a few.
What we're seeing now falls squarely in the "arbitrary changes for no good reason" class - right now I get different results from the same keystrokes depending on the day. I'm not arguing against introducing AI to your platform - I'm arguing against breaking an existing interface to generate some new behaviour when the interface has an established pattern of use, and there are other ways of accomplishing the task. And I'm especially against having the interface change back and forth arbitrarily from day to day - this is needlessly frustrating. Why would you think this is a good idea?