the problem a long migration doesn’t fit in one agent chat. the context fills up and you start over. the fix cursor launched projects in beta on september 10. you talk to a coordinator agent that plans the work and hands it to other agents. the coordinator doesn’t write code itself. the project runs on its own cloud computer, so closing your laptop doesn’t stop it, and it keeps shared context files every agent can read. action open the agents window, pick projects in the sidebar and click new project. name it after the outcome, like “checkout redesign”, not the repo. pick the repo and the coordinator’s model. make your first message research only: ask for a plan, a conventions file and a how-to-test file before any code. tradeoff pro: when one agent works out how to test a service, later agents reuse those notes. con: cursor’s docs say five parallel subagents use about five times the tokens of one, and simple tasks can run slower. the “30% more prs merged” figure is cursor’s own. takeaway use it for work that takes weeks. a one-hour bug fix doesn’t need a coordinator.