Feature request for product/service
Cursor IDE
Describe the request
I’d like Cursor to support workspace- or profile-scoped configuration so that rules, skills, subagents/agents, and optionally MCP can be shared across all projects in a multi-root workspace, without being global to every workspace or duplicated in every repo.
Current behaviour
-
Rules: Only project-level (
.cursor/rules/per repo) or user-level. In multi-root workspaces, only one folder’s rules appear to be used (e.g. first alphabetically), and there is no documented “workspace-level” rules. -
Skills: Project-level (
.cursor/skills/or.agents/skills/) or user-level (~/.cursor/skills/). User-level applies to all workspaces; there is no “only in this workspace” scope. -
Subagents / agents / MCP: Same idea — no workspace-scoped layer.
Desired behaviour
Introduce a workspace-scoped (or profile-scoped) layer that:
-
Applies only when a workspace is open (e.g. when opening a
.code-workspacefile or a multi-root workspace). -
Lives in a well-defined place, for example:
-
Next to the workspace file: e.g. if the workspace file is
~/workspaces/MyProduct.code-workspace, then~/workspaces/.cursor/(or~/workspaces/.cursor/workspace/) holds workspace-level rules, skills, agents, and optionally MCP; or -
A path specified inside the
.code-workspacefile (e.g."cursor": { "configPath": ".cursor-workspace" }).
- Precedence: e.g. workspace → project (repo) → user, so workspace-level can provide shared defaults and repo-level can override.
Use case
-
Multi-root workspace with several repos (e.g. backend, frontend, landing) that should share the same rules, skills, and agent setup (e.g. coordinator, JDs, shared MCP).
-
I want one place to maintain “this workspace’s” AI config and have it apply to all roots, without affecting other workspaces and without duplicating the same rules/skills in every repo.
Related
Thanks for considering this.
Operating System (if it applies)
MacOS