Day 7 receipt
Cursor Projects (beta)
A coordinator agent that plans larger work, hands it to many cloud and local agents and keeps shared context across them.
Launch dayWhat they claimed, quoted word for word · 4
“It maintains context over months of work, delegates tasks to thousands of subagents, and performs recurring work without being prompted.”
Too new to test 'months'; no reports at that scale.
“Each Project maintains a set of files that sync across every cloud and local machine its agents use.”
The shared files aren't contradicted, but the coordinator's checkout of the code itself does not update after merges (staff: expected today).
“Tell the coordinator agent to watch a Slack channel, run on a schedule, or follow all your PRs.”
No solid reports either way.
“Projects are available in beta and rolling out to all users starting today.”
No access complaints found; not enough reports to call it.
Day 7What real users report · 4
In a long-lived Project, the coordinator kept working from an old checkout because it never pulls merged changes. Staff confirmed this is expected today and suggested asking the coordinator to pull.
Staff reply · Open the source
Runtime secrets added for a Project's cloud environment did not save or reach agents. Staff traced it to the Project still pointing at the temporary repository created before it was named.
Staff reply · Open the source
The coordinator asks questions as plain chat messages instead of answerable tiles, so questions get lost in scrollback. Staff said this is intended for now.
Staff reply · Open the source
In a feature-request thread, a user says routing everything through the Project coordinator loses detail because it summarises, and shares a shared-notes-file workaround.
Reply in a staff-answered thread · Open the source