i have been working in product for 10 years, been a head of product, and a founder of multiple companies, and i would literally join cursor’s product team for 6 months just to help them figure out what to do with this. i love their product but it’s crucial to get this right
1 Like
I’m with you, I’m a senior solution architect with a large consulting firm, they should think about engaging some people. They got the funding. But I think its a case of not knowing what they don’t know, because they don’t have the right people and culture in place. Point in fact, if cursor actually had a product manager, they would literally live on this forum. 
Instead, we have community ambassadors and community engineers, who I’m betting are multi-hatting other things as well..
I’m baffled as to why they would do this. Cursor is built on VS Code, arguably the most versatile IDE on the market. The one size fits all solution they’re trying to push is insanely dumb. The out of the box planning tool sucks, and doesn’t do what I want it to do. You’re a company full of software engineers, how is it lost on you that everyone has different needs and workflows? I’m not going to experiment with prompts just so I can circumvent whatever shadow instructions you’ve injected into the planning mode, then append my own massive prompt just to accomplish something I was able to do yesterday. This is a massive time waste.
Way to drop the ball guys. I’m finding another tool that won’t rug pull essential features.
Showing up here again to beat the drum for custom modes. Please bring it back!
1 Like
I just found out (had a break in coding for a couple of weeks for family issues) and I am really angry. Considering canceling my MAX plan right now and here. How could they take this away from me? I had a couple of fine-tuned custom modes I used everyday. Now I would not even attempt to run a larger change!
1 Like
Bumping here to remind the crowd at large!! UpVote this!!
2 Likes
I would like to break this down from a UX perspective.
Some key facts:
-
Switching to a “new” agent is the primary method of managing the context window. Cursor staff have explicitly demonstrated this workflow in at least one or more videos.
-
Adding commands back into the new agent every time you spawn it, is extra user input that can be error prone, subject to un-repeatability, and runs counter to automation patterns.
-
SOME form of agent customization is the most friction-free and obvious pattern to address this.
-
Placing this functionality in the “modes” dropdown is not scalable, also requires an extra user input, and runs counter to UX/UI conventions around agent customization patterns we see across the industry.
Proposal:
Consider allowing user to access custom agents from the agent sidebar. This is a more scalable approach, and is a cleaner UX pattern.
An ALTERNATIVE, but less desirable approach, would be to at least let users clear the context window for a spawned agent. This would somewhat alleviate the number of times a user is forced to set up a new agent for a task, and take a bit of pressure off of the missing custom agents feature.
2 Likes
2026 Jan 11 and still no custom modes… at this point, I don’t know if this will ever be brought back