switching-projects

To switch Cursor workspaces without losing context, you can use a project switching Skill to reorient the active agent into a new project directory. This moves the workspace root without requiring you to open a new window or restart the session.

Yes, you can move an active Cursor conversation into a git worktree by switching the workspace root. The Skill updates the agent's command context to operate within the target worktree directory, allowing seamless codebase transitions.

Jumping between repositories during an ongoing session is best handled by reorienting the agent's root directory. The Skill uses the cursor-app-control MCP to apply the new project path, allowing you to continue work across sibling apps in the same window.

No, switching Cursor projects does not require opening a new window. This Skill applies a new workspace root to the existing session, keeping your conversation history intact while updating the directory context for subsequent commands.

Yes, you need the cursor-app-control MCP installed to switch workspaces mid-conversation. The Skill relies on the move_agent_to_root action from this MCP to update the workspace root and apply the new project directory context.

If your Cursor agent still operates in the old directory after a project handoff, the workspace root was not updated. You must explicitly switch the agent's root directory to the new project path so subsequent commands execute in the correct codebase.