Feature request for product/service
Cursor IDE
Describe the request
In earlier versions of Cursor, Custom Modes allowed users to select a mode and have its behavior persist across the entire conversation. This included:
- consistent rule enforcement
- isolation from default Agent/Ask/Plan behavior
- predictable behavior over multi-turn workflows
- a clear UI mechanism for choosing a mode
In Cursor 2.1.x, Custom Modes were removed.
The suggested alternatives—@file references or slash commands—do not replicate what modes provided:
- they do not persist across turns
- they can fall out of the context window
- they provide no indication that a mode is active
- they do not isolate behavior from other agent types
Because of this, workflows that relied on persistent, selectable modes are no longer possible. A capability that previously existed now has no functional equivalent, and many structured or rule-driven workflows cannot be reproduced under the current architecture.
A mechanism for persistent, per-conversation modes is needed so that these workflows can continue to function.
Operating System (if it applies)
MacOS