A company keeps its shared Cursor rules in a private internal GitHub repository, and each team copies the files into their own projects by hand. What does Cursor's remote rule import support?

The principle — Cursor can import rules directly from any GitHub repository you have access to, public or private. It scans the repository for rule files and places them in an imported folder under the project's rules directory.

Why the key is correct — A private internal rules repository is exactly the intended case. Importing it makes one repository the source of truth and lets Cursor pull and sync the rules, instead of hand-made copies that drift the moment the original is edited.

Why the others are wrong — The public-only reading is what keeps teams copying files by hand. No token needs pasting into a workspace settings file; access follows the GitHub account you already hold. And marketplace mirroring is a separate path with no part in importing rules.

Remember this — Point Cursor at the private rules repository instead of copying files.

Sources — Cursor's Rules documentation.