# Workspace- or profile-scoped Cursor config (rules, skills, subagents, MCP)

**URL:** <https://forum.cursor.com/t/workspace-or-profile-scoped-cursor-config-rules-skills-subagents-mcp/153068>\
**Category:** Feature Requests\
**Tags:** mcp, skills, subagents, rules\
**Created:** [February 26, 2026, 4:49pm UTC](https://forum.cursor.com/t/workspace-or-profile-scoped-cursor-config-rules-skills-subagents-mcp/153068 "2026-02-26T16:49:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amire\_Steve](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/amire_steve/32/88724_2.png) [@Amire\_Steve](https://forum.cursor.com/u/Amire_Steve)\
**Post date:** [February 26, 2026, 4:49pm UTC](https://forum.cursor.com/t/workspace-or-profile-scoped-cursor-config-rules-skills-subagents-mcp/153068/1 "2026-02-26T16:49:00Z")

</div>

### 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:

1. **Applies only when a workspace is open** (e.g. when opening a `.code-workspace` file or a multi-root workspace).

2. **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-workspace` file (e.g. `"cursor": { "configPath": ".cursor-workspace" }`).

1. **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

- [Add Workspace-Specific AI Rule Configuration Feature](https://forum.cursor.com/t/add-workspace-specific-ai-rule-configuration-feature/18743)

- [Cursor Rules files for multi-project workspace](https://forum.cursor.com/t/cursor-rules-files-for-multi-project-workspace/48086)

Thanks for considering this.

### Operating System (if it applies)

MacOS
