Commands should allow model selection - Allow `model` property in command frontmatter

Ideas Feature Requests
1

Feature request for product/service

Cursor IDE

Describe the request

Problem Statement

Currently, running a custom command (via .cursor/commands) uses whichever model is currently active in the Chat or Composer sidebar. This creates a friction-heavy workflow when a specific task requires a specific model:

  • Context Switching: I have to stop, grab the mouse, click the model dropdown, scroll, and select the desired model before typing my /command.
  • Human Error: It is very easy to forget to switch the model, leading to wasted tokens/usage on a model that isn’t optimal for that specific task.

Proposed Solution

Add a model property to the YAML frontmatter of .cursor/commands files. This would allow users to hardcode a preferred model for specific automation.

Example Implementation

---
description: Generate comprehensive unit tests
model: claude-3.5-sonnet
---

Review the selected code and generate Vitest unit tests...

Benefits

  • Speed: A simple /test command would automatically trigger the right model without manual intervention.
  • Consistency: Ensures that complex tasks always use frontier models, while simple formatting tasks can be locked to faster, cheaper models.
  • Keyboard-First Workflow: Keeps the user’s hands on the keyboard, aligning with Cursor’s core philosophy of developer efficiency.

Use Case Examples

  • /refactor: Lock to Claude 3.5 Sonnet for superior logic.
  • /quick-docs: Lock to GPT-4o-mini for rapid, low-cost documentation.
  • /debug: Lock to a model with a larger context window.

Operating System (if it applies)

Windows 10/11