Ability to override settings via cursor/ files (eg allowlist)

Ideas Feature Requests
1

It would be great if configurations for auto-run and command allow-lists could be maintained in the cursor/ directory via a YAML file. This would make them easier to manage, share, and restore.

Right now, settings are fragile — for example, when I clicked the “install CLI” CTA that popped up recently, the installation appeared to hard-reset my Cursor. I lost all my settings, including a command allow-list I’d built over several months. Many of those commands were things I didn’t even know about until Cursor prompted me for permission, so I can’t easily recreate them.

A file-based settings override would also help with onboarding. At work, I’m helping technical writers adopt AI, and we use Cursor partly because of its sharable rules. However, getting the full benefits often means replicating the same settings I’ve refined over time. Since I don’t have admin privileges in our org, this kind of repo- or project-level YAML file for chat, rules, and index settings could be a smart solution. Admins could then choose to allow overrides on a case-by-case basis.

2 Likes
2

Exactly.

Why don’t we have more settings set in .cursor files?
In VSCode we have .vscode/settings.json which is really useful if we want to have different settings for different project. The same should be done for cursor. E.g. allowlists - I would like to have some enabled for one project, and some other allowlists for others.

And i think developers much more prefer to change settings.json file where they see everything clearly then finding manually everything in settings.

3

I’m currently trying to review what’s actually in my command allow list, and can’t even fully read all of it because it’s truncated. Having this as a file just makes a lot more sense.

Does anybody care to share what’s in their allow list? If you could even read it.