Skip to content
Back to skills

Switching Projects

ASecurity

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.

  • 4 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 10, 2026
toolsbashgit

Works with

  • cursor
  • mcp

Security analysis

A100/100

Scanned September 10, 2026

npx -y skills add 0xAidan/polymarket-bot-test --skill switching-projects --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Switching Projects?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Switching Projects
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/0xaidan-switching-projects/badge)](https://www.skillsdirectory.com/skills/0xaidan-switching-projects)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…