Switch Project

How It Works

cursor-app-control

move_agent_to_root

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

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.