Agent can't access .cursor/rules folder to modify them

Bug Reports
1 
et's add tables to /.cursor/rules/ci.mdc to document the 'special' folders, the assumptions, and a table of the env vars, what they're used for, and example values (if certain) @ci.mdc

Restore checkpoint

Thought for 2 seconds

Okay, I will enhance the ci.mdc rule by adding tables to document the key directories, assumptions, and environment variables used in the CI workflow.

I need to read the file first to ensure I append the new tables correctly.

Could not find file '.github/ci.mdc' in the workspace.

Thought for 2 seconds

gemini-2.5-pro-exp-03-25

Version: 0.48.9 (user setup)
VSCode Version: 1.96.2
Commit: 61e99179e4080fecf9d8b92c6e2e3e00fbfb53f0
Date: 2025-04-12T18:45:22.042Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
2

I did two things to make it more likely Cursor will create or update rules in the proper directory, not my original work. I picked these up from a blog somewhere.

  1. I added a editor association for rule files to have the default behavior.

image
image922×485 42 KB

  1. I have a cursor rule I explicitly reference to help guide creating or editing rule content.

Rule snippet

---
description: Use ALWAYS when asked to CREATE A RULE or UPDATE A RULE or taught a lesson from the user that should be retained as a new rule for Cursor
globs: .cursor/rules/*.mdc
alwaysApply: false
---

### Location
- Path: `.cursor/rules/`
- Extension: `.mdc`
- Never modify files outside of `.cursor/rules/` directory when creating or updating rules.

Both of these things together made it more likely for me that when I requested in Agent mode to create or update a rule that it did so successfully.

3

Now this issue is fixed in version 0.49.

1 Like