Cursor rules vs AGENTS.md: which to use (and .cursorrules)
Cursor rules vs AGENTS.md Checked against the official docs: Oct 27, 2026 Cursor gives you three ways to hand your coding agent standing instructions: project rules in .cursor/rules , an AGENTS.md file, and the older .cursorrules file. They overlap, and they work differently. This guide explains each one, which tools read it, and which to pick, with copy-paste examples checked against Cursor's…
Cursor offers three ways to provide instructions for its coding agents: project rules in .cursor/rules, an AGENTS.md file, and the older .cursorrules file. Each of these options works differently and is read by different tools.
AGENTS.md is a markdown file that can be placed in the project root or subfolders. It is an open format supported by multiple coding agents, including Cursor. The agent reads AGENTS.md files in order of specificity, with more specific files taking precedence over broader ones. This format is cross-tool compatible and ideal for plain, always-relevant project instructions, such as setup, test, lint commands, and code style.
In contrast, .cursor/rules/*.mdc files are meant for Cursor-specific rules that only apply in certain situations, such as for specific file patterns or when the agent judges it relevant. These rules can be scoped to individual folders or files by using globs. Cursor also supports User Rules and Team Rules, which are managed through the Customize interface and the dashboard on Team and Enterprise plans, respectively.
While .cursorrules is still functional, it is considered legacy and will be deprecated in the future. Cursor advises migrating from .cursorrules to the .cursor/rules/*.mdc format, as this is the actively supported format for managing project rules.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.