I disagree. That isn't even an interface. And this is the source of so much trouble. The "developer knows best" mindset. The developer will never know exactly when I want coffee, yet so many programs assume my coffee needs are just an algorithm that I secretly obey and just don't know it yet.

The best interface does nothing. It's idle and listens. Everything automatic must be fully transparent and be opt-in. Fully explained if not self-explanatory.

User instruction beats developer assumption every single time. If the user is "wrong" as arbitrarily defined by the developer, the least they can do is kindly instruct and point the user in the "right" direction, not assume, let alone assume they know better than the user about what they want.