Three ways to get a rule into every project
“Global” can mean three different things in Cursor, depending on who the rule is for:
| Option | Where | Applies to | Who sees it |
|---|---|---|---|
| User Rules | Customize > Rules | All your projects, synced to your account | Only you |
~/.cursor/rules files |
Your home folder | Your projects on that machine | Only you, only on that machine |
| Team Rules | Cursor dashboard, by an admin | All repositories of the team | Everyone on the team |
Project Rules in .cursor/rules/ are the opposite: they belong to one repository. How those work is on How do you use Cursor rules.
How to set a User Rule
- Open Customize in the sidebar and go to Rules.
- Add your rule under User Rules as plain text. There is no frontmatter, no globs and no mode: a User Rule is always on for Agent.
- Keep it to preferences that hold everywhere: language of replies, how concise answers should be, how you want explanations, which tools you prefer.
- Sign in on another machine and the rule is there, because it is stored on your Cursor account.
Cursor’s own example of a User Rule is a request for concise replies. That is the right size: something about you, not about a codebase.
The limits
Agent only. Cursor’s help says it plainly: rules only apply to Agent (Chat). They do not change Tab completions, and they do not reach Bugbot when it reviews a pull request. Bugbot has its own rule files.
Lowest priority. All applicable rules are merged, and when they conflict the order is Team Rules, then Project Rules, then User Rules. If your User Rule says “use tabs” and the repository says “use spaces”, the repository wins.
No scoping. A User Rule cannot target a file type or folder. If you need “in Python files, always use type hints” across projects, write it as plain text and let Agent judge, or put the conventions in each repository.
Not a file you can commit. User Rules are not stored as files, which is also why Cursor’s /migrate-to-skills command skips them. Personal procedures you want everywhere fit better as personal skills in ~/.cursor/skills/.
Local files do not travel. Rules you keep as files in ~/.cursor/rules stay on that machine. Cursor’s help notes they do not sync, unlike account User Rules.
The common mistake: putting team knowledge in User Rules
It is tempting to write “our API uses this error format” or “deploys go through staging first” into your User Rules, because then it works in every repository you open. But only your Agent knows it. A colleague’s Agent makes the mistake you already fixed, and when you leave, the knowledge leaves with your account. Anything that is true for the codebase belongs in the repository, as a Project Rule or in AGENTS.md. Anything that is true for the whole organization belongs in a Team Rule. Keep User Rules for how you like to work.
Cloud Agents
Cursor’s Cloud Agent best practices list three levels of rules a Cloud Agent reads: User Rules for your own sessions across all repositories, Team Rules for everyone, and repo rules committed in .cursor/rules/. So a User Rule follows you into your Cloud Agent sessions too. Project rules and AGENTS.md only reach a Cloud Agent if they are committed to the repository it checks out.
What this means for a team
User Rules are the right place for personal taste and the wrong place for shared knowledge. On a Team or Enterprise plan, an admin can turn a rule that everybody keeps adding by hand into a Team Rule, and choose to enforce it so nobody can switch it off. Without such a plan, the shared route is the repository. See How do you share context and team rules in Cursor.
Where Bombos fits
User Rules give one person a memory that follows them across projects, but only inside Cursor and only for that person. Bombos is a plugin that gives every AI tool your team uses, Cursor, Claude Code, Copilot, ChatGPT and your own agents, one shared memory with team knowledge and rules it learns from corrections, traceable, in the cloud or on your own server. A single developer can start with it for their own agents, as a personal layer that also works outside Cursor.
Related questions
Is there a global .cursorrules or .mdc file?
User Rules are set in Customize > Rules and stored on your account, not as a file. Cursor's help notes that files in ~/.cursor/rules stay on the local machine and do not sync. The old .cursorrules file is legacy and per project.
Do User Rules work in Cloud Agents?
Cursor's Cloud Agent best practices list User Rules as one of three levels Cloud Agents read, for your own sessions across all repositories. Repo rules only apply when they are committed to the repository the agent checks out.
Can my teammates see my User Rules?
No. They are tied to your account. To give the whole team a global rule, an admin sets it as a Team Rule in the dashboard on a Team or Enterprise plan.
Do User Rules affect Tab completions?
No. Cursor states that rules only apply to Agent (Chat), not to Tab completion or Bugbot pull request reviews.
