A developer copies `api.mdc` into a nested folder and edits the copy, expecting the nearer file to replace the original. What happens once both rules' conditions match?

Easycursorrulesfile-pathoverridesproject-rules

Last reviewed 21 Aug 2026

The file with the more recent modification time wins, and the older copy is skipped for that conversation.
The nearer copy shadows the original, in the way a nearby config file overrides an outer one.
Cursor reports a name collision and holds both files back until one of them has been renamed.
Both rules apply, because Cursor identifies a rule by its full file path rather than its name.Correct answer

Show answer & explanation

Correct answer: D. Both rules apply, because Cursor identifies a rule by its full file path rather than its name.

Explanation

The principle — Cursor identifies a rule by its full file path, not by its filename alone. Two rules with the same filename in different folders both apply if their conditions match.

Why the key is correct — The copy does not displace the original. Both files are injected into context, so the developer now carries two sets of instructions, and wherever the copy contradicts its original, Agent is handed both.

Why the others are wrong — The shadowing instinct comes from config cascades, where a nearer file overrides an outer one, and the rules system has no such override. Nothing is held back pending a rename. And modification time has no bearing on loading, so the older copy is still very much active.

Remember this — Copying a rule adds it; to replace one, edit or delete the original.

Sources — Cursor's Rules documentation.

Sources

Primary sourceRules — Cursor · accessed 19 Aug 2026
“Two rules with the same filename in different folders both apply if their conditions match.”

Practise 10 questions on this topic

Take Cursor Basics — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.

Start the test

A developer copies `api.mdc` into a nested folder and edits the copy, expecting the nearer file to replace the original. What happens once both rules' conditions match?

Easycursorrulesfile-pathoverridesproject-rules

Last reviewed 21 Aug 2026

The file with the more recent modification time wins, and the older copy is skipped for that conversation.
The nearer copy shadows the original, in the way a nearby config file overrides an outer one.
Cursor reports a name collision and holds both files back until one of them has been renamed.
Both rules apply, because Cursor identifies a rule by its full file path rather than its name.Correct answer

Show answer & explanation

Correct answer: D. Both rules apply, because Cursor identifies a rule by its full file path rather than its name.

Explanation

The principle — Cursor identifies a rule by its full file path, not by its filename alone. Two rules with the same filename in different folders both apply if their conditions match.

Remember this — Copying a rule adds it; to replace one, edit or delete the original.

Sources — Cursor's Rules documentation.

Sources

Primary sourceRules — Cursor · accessed 19 Aug 2026
“Two rules with the same filename in different folders both apply if their conditions match.”

Practise 10 questions on this topic

Take Cursor Basics — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.

Start the test

A developer copies `api.mdc` into a nested folder and edits the copy, expecting the nearer file to replace the original. What happens once both rules' conditions match?

Related questions

A developer copies `api.mdc` into a nested folder and edits the copy, expecting the nearer file to replace the original. What happens once both rules' conditions match?

Related questions