This is a very interesting idea, I'm sure it isn't going to happen, and while I won't quite promise I won't use it, I'm going to be very reluctant and slow to do so, for several reasons:<p>1. Imagine having a device that simply did whatever you needed, only, physically. Would you use? It would be hard not to. But the resulting atrophy would be very dangerous to you. There is a certain amount of effort you need to exert on your own, or you will lose the ability to exert any effort. But your effort is what you're getting paid for....<p>2. Extensive use of this tool would impact its own effectiveness, by depriving it of training data. It would eventually stereotype you into a rut, whether you liked it or not. This would be the equivalent of an over-stereotyped recommendation list for YouTube or TikTok, only converted into my work life. Not necessarily a good idea.<p>3. This would give more power than I particularly care for over to the person designing this tool. Defaults have a lot of power as it is; witness the power of the default search engine in a browser. Putting my entire computer life at the disposal of someone else's choice of defaults like that is even worse, especially with the amount of "intelligence", artificial or otherwise, that would be deployed in the choices. Yes, yes, in a perfect world it would just neutrally do what you want and the person developing it would simply ethically resist all offers to skew the answers for profit. In reality, well, basically, lol, no, that's not what will happen.<p>All that said, like I said, it is going to happen. Though it will take more than 12-18 months. It is not completely clear how to map a "language model" to this task, and I think it will take longer. (I mean "not completely clear" straight. I don't mean that as a rhetorically-lightened "I don't think it's possible"; I think it is. However, I suspect the stupid obvious ideas will need significant refinement before they work, and the development cycle is going to need some time to go around the loop a few times.) Also, this would be a lot easier if we lived in a world where something like Appletalk was still alive and everything was able to be interacted with in such a standard way. While the ML task for a tool like this is nontrivial, most likely the bulk of the work by person-hour is going to be hooking it to all the bespoke APIs and GUI automation and all the other crap work of trying to get this to work with actual tools correctly. (I mean, it's darned near "reimplementing Appletalk, except from the outside and without help from the OS vendor this time".)