Is .cursorrules deprecated?
Cursor's documentation labels .cursorrules as legacy. It is the older single-file format, and new rules should go in .cursor/rules as .mdc files or in AGENTS.md.
The .cursorrules file is Cursor's original single-file format; .cursor/rules/*.mdc is the current one, with frontmatter that scopes each rule. Cursor marks .cursorrules as legacy.
Last verified 2026-11-13 against the vendor documentation.
| .cursorrules | .cursor/rules/*.mdc | |
|---|---|---|
| Status in Cursor | Legacy | Current project rules |
| Files | One file at the root | Any number, in folders |
| Frontmatter | None | description, globs, alwaysApply |
| Scoping | Always applies | Always, by glob, by relevance, or on mention |
| Other readers | Cline auto-detects it; Zed if first match; Windsurf imports its own legacy files, not this one | Cursor only |
A single file that is always included grows until it is mostly noise for any given task. Project rules let you keep the always-on part small and attach the rest only where it matters, such as test conventions for test files or component rules for src/components. The frontmatter is what makes that possible:
---
description: Conventions for React components
globs: src/components/**/*.tsx
alwaysApply: false
---
- Use named exports, not default exports.
- Keep components under 200 lines; extract subcomponents into the same folder.
Even in those cases AGENTS.md is a better target, because Cline and Zed both read AGENTS.md too.
Cursor supports AGENTS.md at the root and in subdirectories, as a plain alternative to rules. The clean split is: shared instructions in AGENTS.md, which every agent reads, and only Cursor-specific or glob-scoped rules in .mdc files. The 2prompt generator writes one always-on project.mdc that points to AGENTS.md without repeating it: Cursor already loads AGENTS.md on its own, so a copy would only spend context twice. Note that an @file mention in a rule points to a file rather than inlining it.
Long .cursorrules files usually mix three kinds of content: facts about the project, rules for everyone, and conventions for one corner of the code. Sorting lines into those buckets makes the migration mechanical.
Expect the always-on part to shrink noticeably. Many lines in old .cursorrules files are restatements of the same idea, or advice so general that no agent can act on it, and the linter will point those out. What remains is shorter, easier to review and read by more tools.
Do the split in one pull request so reviewers can see every line move from .cursorrules into its new home. Reviewing the old and new files side by side makes it easy to spot a rule that was lost, duplicated or quietly changed during the move. After it merges, ask one or two teammates to work as normal for a few days before deleting any backups.
More detail: Cursor rules format.
Cursor's documentation labels .cursorrules as legacy. It is the older single-file format, and new rules should go in .cursor/rules as .mdc files or in AGENTS.md.
You can, but it is a common source of contradictions because the two files drift. Migrate the content and delete .cursorrules so there is one place to edit.
Most often it has a .md extension. Project rules must be .mdc files with frontmatter. Also check that a non-global rule has globs or a description, otherwise it only applies when mentioned.
Not that we verified. The .mdc format is Cursor-specific. Put rules you want every agent to follow in AGENTS.md, which Cursor also reads.