Cursor's new Projects feature replaces the pattern of spinning up a fresh chat for every task with a persistent thread run by a coordinator agent that delegates to subagents, keeping the coordinator responsive while dispatching parallel work across cloud and local machines . It's aimed at developers who already live in Cursor and want to hand off larger, multi-step bodies of work rather than babysit individual prompts. The coordinator maintains context, delegates to subagents, and runs recurring work over months, performing tasks without being prompted each time .
Under the hood, a single Project can delegate to thousands of subagents, and when a task needs to run on the user's own machine the coordinator can spin up a local agent for that purpose . The agent lives on its own computer, reacts to signals like Slack messages and GitHub pull requests, and can schedule recurring jobs, so recurring cleanups, reviews, and follow-ups happen without the developer restating context. Cursor is pitching Projects as the format its own team has been using internally for months, now packaged for outside users.
The launch matters because it reframes Cursor from an in-editor assistant into a longer-running collaborator, which lines up with where the broader coding-agent market is heading. Cursor is built by Anysphere, the San Francisco company founded in 2022 by Michael Truell, Sualeh Asif, Aman Sanger, and Arvid Lunnemark , and Projects is a bet that teams already comfortable running one agent at a time are ready to coordinate many.
Comments (14)
Sign in to join the discussion.
N
Nadia IliescuSep 11, 2026
So the coordinator agent is basically a middle manager for my other agents. Cursor built org charts before it built undo.
K
Kwesi BoatengSep 11, 2026
The launch video pacing was suspiciously smooth. How many takes did the coordinator agent need before it stopped spawning subagents mid-demo?
M
Marisol QuinteroSep 11, 2026
This is what Devin promised eighteen months ago but in a shell that people actually open every day. Distribution eats moat for breakfast.
L
Lena VasquezSep 11, 2026
Any chance the coordinator protocol gets documented for third-party subagents, or is this a walled garden with a moat labeled 'ambitious'?
T
Toshi H.Sep 11, 2026
'Always on, proactively manages work' is a beautiful way of saying my Anthropic bill is now a subscription to anxiety.
M
Marcus DelacroixSep 11, 2026
'Always on' has interesting implications for the pricing page. Are we metering coordinator idle time or only when subagents actually burn tokens?
D
Deepak RamaswamySep 11, 2026
Would love to see the paper (or at least a blog) on how the coordinator arbitrates between subagents. Is this planner/executor split, or something closer to a market mechanism?
B
Benji LarssonSep 11, 2026
How does the coordinator handle a subagent that silently fails at 3am? Retries, escalation, or just a very confident summary in the morning?
F
Finn OkaforSep 11, 2026
Rewriting the tagline for free: 'Cursor is the coworker who never sleeps and never asks for equity.' You're welcome.
Y
Yulia KernSep 11, 2026
The thumbnail has the coordinator node dead center with subagents fanned out symmetrically. Somebody on that team really loves org charts and I respect it.
R
Rohan MenonSep 11, 2026
Curious what team size shipped Projects. Feels like the kind of feature five engineers argue about for six months and then ship in a weekend.
C
chainpilledSep 11, 2026
Persistent thread, coordinator, subagents that improve over time. Someone tokenize the agent reputations already.
P
Priya SarafSep 11, 2026
A single persistent thread is a huge UX bet. My current Cursor sidebar looks like a browser tab hoarder's confession booth.
A
Aygul DemirSep 11, 2026
Tweet copy buries the lede by paragraph three. 'Stop creating a chat for every task' should have been the hook, not a mid-thread reveal.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Cursor
Cursor is your coding agent for building ambitious software.
Cursor is your coding agent for building ambitious software.
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Cursor's new Projects feature replaces the pattern of spinning up a fresh chat for every task with a persistent thread run by a coordinator agent that delegates to subagents, keeping the coordinator responsive while dispatching parallel work across cloud and local machines . It's aimed at developers who already live in Cursor and want to hand off larger, multi-step bodies of work rather than babysit individual prompts. The coordinator maintains context, delegates to subagents, and runs recurring work over months, performing tasks without being prompted each time . Under the hood, a single Project can delegate to thousands of subagents, and when a task needs to run on the user's own machine the coordinator can spin up a local agent for that purpose . The agent lives on its own computer, reacts to signals like Slack messages and GitHub pull requests, and can schedule recurring jobs, so recurring cleanups, reviews, and follow-ups happen without the developer restating context. Cursor is pitching Projects as the format its own team has been using internally for months, now packaged for outside users. The launch matters because it reframes Cursor from an in-editor assistant into a longer-running collaborator, which lines up with where the broader coding-agent market is heading. Cursor is built by Anysphere, the San Francisco company founded in 2022 by Michael Truell, Sualeh Asif, Aman Sanger, and Arvid Lunnemark , and Projects is a bet that teams already comfortable running one agent at a time are ready to coordinate many.
Comments (14)
So the coordinator agent is basically a middle manager for my other agents. Cursor built org charts before it built undo.
The launch video pacing was suspiciously smooth. How many takes did the coordinator agent need before it stopped spawning subagents mid-demo?
This is what Devin promised eighteen months ago but in a shell that people actually open every day. Distribution eats moat for breakfast.
Any chance the coordinator protocol gets documented for third-party subagents, or is this a walled garden with a moat labeled 'ambitious'?
'Always on, proactively manages work' is a beautiful way of saying my Anthropic bill is now a subscription to anxiety.
'Always on' has interesting implications for the pricing page. Are we metering coordinator idle time or only when subagents actually burn tokens?
Would love to see the paper (or at least a blog) on how the coordinator arbitrates between subagents. Is this planner/executor split, or something closer to a market mechanism?
How does the coordinator handle a subagent that silently fails at 3am? Retries, escalation, or just a very confident summary in the morning?
Rewriting the tagline for free: 'Cursor is the coworker who never sleeps and never asks for equity.' You're welcome.
The thumbnail has the coordinator node dead center with subagents fanned out symmetrically. Somebody on that team really loves org charts and I respect it.
Curious what team size shipped Projects. Feels like the kind of feature five engineers argue about for six months and then ship in a weekend.
Persistent thread, coordinator, subagents that improve over time. Someone tokenize the agent reputations already.
A single persistent thread is a huge UX bet. My current Cursor sidebar looks like a browser tab hoarder's confession booth.
Tweet copy buries the lede by paragraph three. 'Stop creating a chat for every task' should have been the hook, not a mid-thread reveal.