Cursor Custom Modes: Pin Any Skill as an Always-On Mode
Cursor added Custom Modes, allowing any skill to be pinned in the chat so it stays active for the whole session rather than being invoked once. Users pick a skill from the / menu and press Option+Enter (Mac) or Alt+Enter (Windows), or choose Use as Mode, to keep the agent focused on that skill's playbook throughout a conversation. Cursor describes the feature as effectively turning any skill into an "always-on" mode, making it easier to keep an agent consistently following a specific workflow.
Key Takeaways
- Any existing skill can now be turned into a persistent mode with a single keystroke (β₯β / Alt+Enter) from the slash menu, no separate configuration needed.
- Custom Modes keep the agent's behavior consistent across an entire chat session, instead of a skill applying only to the single turn where it was invoked.
- The feature effectively reframes Cursor's existing Skills marketplace as a source of always-on modes, extending the value of skills users or teams have already built.
- Custom Modes are designed to pair with
/goal, letting a long-running autonomous agent follow both a fixed objective and a fixed playbook simultaneously. - This lowers the friction of enforcing team-specific conventions (review checklists, refactor patterns, testing standards) without needing to repeat instructions every turn.
- The change fits Cursor's broader August 2026 theme of making agents operate more independently and predictably over long sessions rather than needing constant re-steering.
Turning skills into persistent modes
Cursor's Skills system already let users define reusable playbooks the agent could invoke on demand. With this release, Cursor introduced Custom Modes, which let any skill be pinned into the chat so it stays active for an entire session instead of firing once and fading out.
How it works
From the / slash menu, a user selects a skill and presses β₯β (Mac) or Alt+Enter (Windows), or chooses Use as Mode, to promote it into a Custom Mode. Once pinned, the mode keeps the agent focused on that skill's instructions for the duration of the chat β Cursor frames this as effectively making any skill "always on," rather than a one-time invocation.
Why it matters
Previously, keeping an agent consistently following a particular workflow β say, a strict code-review checklist, a specific refactor pattern, or a team's testing playbook β required re-invoking the skill or repeating instructions across turns. Custom Modes remove that friction: once pinned, the skill's guidance persists automatically across the session, similar to how built-in modes (like Plan Mode) keep the agent operating under a consistent set of rules.
This also complements the other agent-autonomy features shipped in the same release. Custom Modes can be paired with /goal to give a long-running agent both a persistent objective and a persistent playbook for how to pursue it, or with subagents running in isolated environments to keep every parallel worker following the same standard operating procedure.