The daily ingest already lists what Cursor published. This post is the editorial cut: which of those surfaces belong in .cursor/, and which stay product buttons.
Since the 19 August harness we added kits for Custom Modes, subscriptions, and /goal. The next six weeks shipped a different layer — bigger work, empty repos, and the last mile after the diff is green.
Start from scratch is still a first slice
On 27 August, cloud agents stopped requiring GitHub. You pick Start from scratch, prompt, get a forwarded preview, then Create repo on Origin when you like the build. Vercel publish is a later click.
That is not permission to ask for a platform. The Start from scratch prompt on this site is the first-slice brief with the Origin/Create-repo step written in. Pair it with Studio stack if the slice is a Next.js UI.
Projects keep memory. Coordinators do not write the feature
Cursor Projects (10 September, beta) are for a feature, a migration, or an app that should last months. The coordinator plans, delegates, and brings work back. Shared files sync across the cloud and local machines those agents use. Subscriptions still need a wake instruction and a stop condition.
The Project coordinator skill and Brief this Project prompt exist so the next agent is not re-onboarded from a blank chat. Project pack is the recipe.
Self-hosted is a placement decision
Self-hosted machines (2 September) move tool execution onto a laptop (My Machines) or a team pool. Code, builds, and secrets can stay on your network. Planning and inference stay in Cursor. Cursor-hosted remains the default.
The Self-hosted worker skill is the decision list. It is not a setup wizard for AWS Lambda or E2B.
Last mile is text plus bots, not a bot wrapped as a kit
On 23 September Cursor launched two Teams/Enterprise bots: Security Review (exploitable bugs on every PR; style stays with Bugbot) and Rollouts (a monitoring plan, then change health per environment). Enable those from Automations. We will not ship a fake dashboard for them.
What we will ship is the same job in files the editor agent can follow:
- Security PR review — trace user input, patch, no PoC
- No secrets in git — always-on, including tokens pasted in chat
- Make this change observable — intended effect, signals you already have, gaps
- Last mile — the recipe
What we did not turn into kits
Harness token-efficiency is not a file you unzip. Directory plugins still belong on /updates, not in this studio. Grok 4.7 is a model picker — the brief lives in Grok long run, not in a restyle of the site.
Packs
Project pack for work that should remember. Last mile for the stretch after the feature works. Always-on agent is still the harness pack from August.