Cursor Skill

switching-projects

Switch the current Cursor workspace to a different project directory using the cursor-app-control MCP. Use when the user asks to switch projects, open another repo, jump to a different codebase, or move to a worktree.

LLM Mart · 0 points · 25 views 1 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download spencerpauly-awesome-cursor-skills-resources_switching-projects-99cd265.zip · 1 KB
Part of spencerpauly/awesome-cursor-skills — 65 skills

Install

skills CLI npx skills add https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/switching-projects
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install spencerpauly-awesome-cursor-skills@llmmart
Git git clone https://github.com/spencerpauly/awesome-cursor-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole spencerpauly/awesome-cursor-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Switch Project

Use this skill when the user wants to switch to a different project, open another codebase, or move the current conversation to a different workspace root.

How It Works

Cursor has a built-in MCP server called cursor-app-control with a tool called move_agent_to_root that changes the agent's active workspace directory. This lets you switch projects mid-conversation without opening a new window.

Steps

  1. Ask or infer the target project — if the user says "switch to my-app", search for it. Common project locations:

    • ~/Documents/development/
    • ~/projects/
    • ~/code/
    • ~/repos/

    List directories in the likely parent folder to find the project:

    ls ~/Documents/development/
    

    If ambiguous, ask the user which project they mean.

  2. Switch the workspace — call the cursor-app-control MCP tool:

    Tool: move_agent_to_root
    Arguments: { "rootPath": "/Users/<username>/Documents/development/<project-name>" }
    

    This updates the visible workspace, file tree, and default working directory for all subsequent commands.

  3. Orient in the new project — after switching, briefly describe what you see:

    • Read the project's package.json, README.md, or equivalent to understand the stack.
    • Run git status to show the current branch and state.
    • List the top-level directory structure.

Creating a New Project

If the user wants to start a new project and switch to it:

  1. Call create_project with the desired path — this creates the directory and initializes a git repo.
  2. Call move_agent_to_root to switch into it.
  3. Begin scaffolding.

Notes

  • This only works if the cursor-app-control MCP server is enabled.
  • The switch happens in the current conversation — no new window is opened.
  • All file paths in subsequent tool calls will resolve relative to the new root.
  • You can switch back to the original project the same way.
Files (awesome-cursor-skills)
  • SKILL.md 2.2 KB
    ---
    name: switching-projects
    description: Switch the current Cursor workspace to a different project directory using the cursor-app-control MCP. Use when the user asks to switch projects, open another repo, jump to a different codebase, or move to a worktree.
    ---
    
    # Switch Project
    
    Use this skill when the user wants to switch to a different project, open another codebase, or move the current conversation to a different workspace root.
    
    ## How It Works
    
    Cursor has a built-in MCP server called `cursor-app-control` with a tool called `move_agent_to_root` that changes the agent's active workspace directory. This lets you switch projects mid-conversation without opening a new window.
    
    ## Steps
    
    1. **Ask or infer the target project** — if the user says "switch to my-app", search for it. Common project locations:
       - `~/Documents/development/`
       - `~/projects/`
       - `~/code/`
       - `~/repos/`
    
       List directories in the likely parent folder to find the project:
    
       ```bash
       ls ~/Documents/development/
       ```
    
       If ambiguous, ask the user which project they mean.
    
    2. **Switch the workspace** — call the `cursor-app-control` MCP tool:
    
       ```
       Tool: move_agent_to_root
       Arguments: { "rootPath": "/Users/<username>/Documents/development/<project-name>" }
       ```
    
       This updates the visible workspace, file tree, and default working directory for all subsequent commands.
    
    3. **Orient in the new project** — after switching, briefly describe what you see:
       - Read the project's `package.json`, `README.md`, or equivalent to understand the stack.
       - Run `git status` to show the current branch and state.
       - List the top-level directory structure.
    
    ## Creating a New Project
    
    If the user wants to start a new project and switch to it:
    
    1. Call `create_project` with the desired path — this creates the directory and initializes a git repo.
    2. Call `move_agent_to_root` to switch into it.
    3. Begin scaffolding.
    
    ## Notes
    
    - This only works if the `cursor-app-control` MCP server is enabled.
    - The switch happens in the current conversation — no new window is opened.
    - All file paths in subsequent tool calls will resolve relative to the new root.
    - You can switch back to the original project the same way.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related