Nested agents.md files not being loaded

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

docs say that nested agents.md files should be loaded when agents work in those directories, but in my testing they do not every get appended automatically. Only the root agents file is appended automatically.

Link to docs: Rules | Cursor Docs

Steps to Reproduce

  1. Have nested agents.md files
  2. Open new agent, ask to make a minor edit to a file deep in the repo.
  3. Ask agent to check what context was loaded automatically.
  4. Agent will respond that only the root agents.md file was loaded.

Expected Behavior

All Nested agents.md files get loaded automatically if agent makes an edit in a nested directory.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.54
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The AGENTS.md file is not automatically added to the AI chats.

Steps to Reproduce

Create an AGENTS.md file. Put any instruction in there. Chat with AI. AI will ignore instructions.

Manually include the file in chat. AI will follow instructions.

Expected Behavior

AGENTS.md should be included automatically in every agent call.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.54 (Universal)
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. You’re right: nested AGENTS.md files should auto-load when the agent works in those directories.

This looks like a bug in the nested AGENTS.md functionality.

I’ll pass this to the team. As a temporary workaround, you can manually add the nested AGENTS.md files to the agent’s context using @AGENTS.md or by referencing the file directly.

Yeah but that kinda defeats the purpose. I’d suggest updating your documentation to reflect that this functionality is not yet supported.

1 Like

This seems to have been fixed now: Rules | Cursor Docs