Cursor ACP is not loading rules correctly

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Title: Support path resolution from file URIs in rule glob pattern matching

Description: When external tools (like ZED IDE) send file references via ACP (Additional Context Protocol) as file URIs (e.g., file:///path/to/admin.controller.spec.ts), Cursor’s rule engine cannot match them against glob patterns in project rules.

Current behavior:

Rules with globs: **/*.controller.spec.ts don’t load when the file is referenced as [ACP resource_link] admin.controller.spec.ts (file:///…)
Rules DO load when the file is referenced with full relative path: apps/admin.controller.spec.ts
Desired behavior: Cursor should extract and normalize the project-relative path from file URIs so glob patterns can match correctly, enabling seamless integration with external IDE plugins.

Impact: This would enable better IDE integration for tools like ZED that pass file context as URIs rather than relative paths.

Steps to Reproduce

install ZED IDE
Create a cursor rule that’s this YAML heder:

---
alwaysApply: false
globs: **/*.controller.spec.ts
---

use ZED AI chat to refernce a file and then ask what rules got loaded - you will see that applicable rules are not loaded

Expected Behavior

I expect acp to load rules based on files that agent reads and based on ACP resource_links provided

Additional ACP context:
[ACP resource_link] admin.controller.spec.ts (file:///code/worktrees/regal-heath/src/controllers/admin.controller.spec.ts)
[full file contents included]

Operating System

MacOS

Version Information

agent version - 2026.07.23-e383d2b

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hey @Karlis_Melderis
I was able to reproduce this on my end: when a file comes through ACP as a resource_link (the shape Zed sends), glob-scoped rules don’t attach, even though the file contents are already in context. Rules do attach if you name the same file by project-relative path in the message text.

Until this is fixed, two workarounds that work today:

  1. Set alwaysApply: true on the rules you need in ACP/Zed sessions
  2. Reference the file by relative path in the chat text (so the agent actually reads it), instead of relying on the attachment alone

We’ve let the team know and this is an issue we’re tracking. I’ll post here when there’s an update.