Cursor Kills Taskmaster with This Update!

We don't necessarily need to know how to solve the problem. We just need to know how to communicate the problem to be solved in more effective way. Cursor. So the news they've updated it to 1.2. Don't know where 1.1 went but they've updated to 1.2 which introduces tasks. They've improved the long horizon task as well which means it can basically run for a long long time. You can search pull requests. You can cue messages up. So while it's like doing its thing, you can like line some stuff up. I hope that all gets sent as one prompt because you can save a lot of tokens by making sure that everything's in one prompt. And so 1.2 is pretty good. Now, the to-do list is something I've been really playing around with. One thing I've been trying to nail is this thing called Taskmaster. Taskmaster is a way to create a PRD, product requirements document, or creating tasks for your product that you you then get the AI agent to run through those tasks and code it all up and all the rest of it. Taskmaster is gaining a lot of traction. this methodology of creating tasks for your coding is gaining a lot of traction and so cursor now they've introduced tasks natively inside the UI is this not just a list of text what is so special about it except it's UI and you know being a nice UX as well so I think it's a combination of two things it's it's showing you the reasoning and it's more so that it's it's planning out and giving you like the opportunity to step in to make sure that it's not going to go off and do just some random crap for you. It's just the way to now AI assist coding creating tasks. It's breaking those down into subtasks and Taskmaster enabled that, but now we're getting it natively. I'm sure you can break down these tasks into further subtasks to be honest. So, I think that it's um a welcome addition. We're starting to just finalize what AI assisted coding looks like. And it's a combination of memories. It's a combination of tasks. It's a combination of planning. And it's putting less emphasis on the actual writing and understanding of code and more in the planning and the architecture around the lines. We are becoming managers. We don't necessarily need to know how to solve the problem. We just need to know how to uh communicate the problem to be solved in an in more effective way. Like a analogy that I give to that is we are moving from being the pilot having a co-pilot to us becoming the co-pilot having AI being the pilot. This is part of a larger conversation on my show Command AI which we stream live every single week. We discuss the news and all things related to AI in the world of design and web. Catch us next week and join in the banter.