I believe that the potential of custom modes is to be used in sequence and combined, but sometimes we need 2 different modes to work on a single step of a task and we need to choose between one of them to be able to use other modes in other steps
1 Like
Thanks for the feedback about custom modes! You make a really good point about needing multiple modes for different steps of the same task. I’ll make sure to pass this along to the team about increasing the limit beyond 5
For now, you might want to check out some example modes in our docs (Cursor – Custom Modes) to help optimize your current limit - there might be ways to combine some functionality into fewer modes depending on your workflow
The team is always looking to improve the custom modes feature, so this kind of feedback is super helpful
1 Like
Yeah, I was also thinking about combining two modes into one, so you could use a single mode at two different points in a task. If it’s something simpler and similar, like a ‘Refactor’ or ‘Debug’ mode, maybe a combined prompt for both could work well. But, in my experience, when you’re using more complex and specific modes one after the other, it makes the response more accurate, faster, and more powerful. I really think this was a great addition in the V.49 features.
And thank you very much for the feedback and attention, your work is amazing!
Hello there. Yeah, I found the Roo’s implementation is quite nice.
- Instead of CTRL+I to go to Agent mode, I like Roo’s feature to cycle them instead
- I also like how with Roo, I can just edit a JSON to create and edit the mode. I found Cursor’s implementation annoying for wanting to experiment different pre-prompt and setting
@joaopf Hmm coming from Roo side, I do think being very very very specific gets you better quality and robust code, so I found it better to separate Refactor and Debug
1 Like
Just wanted to throw support behind this. This would be incredibly powerful, and the arbitrary limit of 5 is just bizarre.