I was wondering how to put my private rules (the team I work with have very different workflows) in a cloud agent without commiting them. Rules are an essential part of my workflow, and I miss them when building with cloud agents, if we could make this happen, I would love this.
Thx for the help if someone has a workarroung
Do you need the same private rules for every Cloud Agent run, or different private rules for each team or repository? The first case may fit User Rules, while the second needs a separate private configuration layer that Cloud Agents can access without committing it.
I also considered User Rules, but I’m now interested on how would you solve the second approach ?
I checked the current options more closely. There is no built-in private rule set scoped to one Cloud Agent repository yet.
The safe interim split is: keep non-sensitive team conventions in the repo, use User Rules only for personal preferences that are safe across every repo, and put the small repo-specific constraints for each run in the reviewed launch prompt. I would not use secrets or environment variables as hidden rule storage.
If those private rules are essential for safe operation, I would keep that work in a supervised local workflow until Cursor adds dashboard-managed private rules that can be assigned to selected repositories.
Thank’s a lot for checking, do you think this will appear ?
I could not find a public roadmap confirming that this is planned, so I would not promise it.
But the gap is real: current options are either user-wide, team-wide, or committed to the repository. Private rules scoped to selected Cloud Agent repositories would be a useful fourth layer. I think this is worth a focused feature request.
Hey @Yann_Baelli,
Building on @AllIN’s split: for prefs that should apply to every Cloud Agent run, put them in User Rules (Cursor Settings → Rules). They’re account-scoped, nothing to commit, and Cloud Agents pick them up - see best practices.
For different private rules per team/repo without committing: no first-class surface yet. Keep shared conventions in the repo, personal cross-repo prefs in User Rules, and small repo-specific constraints in that run’s launch prompt. If you need fuller private file rules, a custom Cloud Agent environment can install them outside the checkout and expose them at /.cursor so discovery finds them (layout reference).
No timeline to share on a dedicated private per-repo surface. We’ll keep tracking interest here - if others want the same, chime in.