Cursor Orchestrate (/orchestrate)
Cursor skill that recursively spawns agents via the Cursor SDK for large tasks. Internal usage cited: autoresearch on skills (~20% token reduction with better evals), backend cold-start reductions (~80%).
Current Source Snapshot
As of 2026-06-30, Cursor's marketplace describes /orchestrate as a plugin skill that fans a large task out across parallel Cursor cloud agents via the Cursor SDK. The source repo cursor/plugins is on main at 0452e08a314c03621ec5ac1324f1ad1dd824f1a4, has no GitHub releases/tags, no license field exposed by the API, and GitHub reports 2,183 stars and 169 forks. The marketplace skill description says to use it only when the user explicitly types /orchestrate <goal>; do not invoke it autonomously. Source: Cursor Marketplace, 2026-06-30; Source: GitHub API; git ls-remote, 2026-06-30
When to use
- Ambitious refactors spanning many files/packages
- Research sweeps that fan out across the wiki + repos
- Any workflow already scripted against
@cursor/sdkwhere parallel child agents help
/orchestrate is the in-IDE, recursive fan-out pattern; the Cursor SDK (@cursor/sdk) is the programmatic runtime underneath it — see that page for invocation patterns (Agent.prompt / Agent.create / Agent.resume) and local vs. cloud runtimes. Install/follow current Cursor docs for the /orchestrate skill — the surface evolves with Cursor releases. Source: User product summary, 2026-05-11
Live signal is still thin but directionally consistent: recent last30days results found one r/cursor thread using the Cursor SDK for iterative sub-agent workflows, one r/LocalLLaMA thread evaluating it for codebase exploration, and the Cursor blog/HN announcement for programmatic agents. Treat this as emerging tooling, not settled community practice. Source: last30days "Cursor SDK", 2026-05-12
Verifier Loop
The durable pattern is not "spawn more agents." It is planner -> worker -> verifier -> retry. Cursor's self-thread says planners spawn workers that write code and verifiers that run it; if verification fails, the planner spawns another worker to fix the failure. This belongs in Browser Testing Skills as a high-blast-radius orchestration mode: use it for genuinely large goals, keep each worker bounded, and make verification the gate between waves. Source: X/@cursor_ai self-thread, 2026-05-07
Stack fit (Kevin)
- Wiki-wide research sweeps — fan child agents out across
wiki/and linked repos for source-compile / radar automations instead of one serial agent. - Large refactors in Kevin's repos — multi-package edits where each child agent owns a slice; pairs with the worktree-first git workflow.
- Built on Cursor SDK — same runtime as Kevin's
code-bugfix/project-briefingcloud runners; orchestrate is the recursive-fan-out skill, the SDK is the programmatic layer beneath it. - Dev-infra only, not Dedalus product — like the SDK, this is for Kevin's own tooling; customer-facing agents should use an owned loop rather than the IDE fan-out skill.
Timeline
- 2026-06-30 | Deep-reviewed the
/orchestratebookmark, repaired local thumbnail media, resolved the marketplace andcursor/pluginssource, and promoted the planner/worker/verifier/retry pattern into Browser Testing Skills. Current source snapshot:cursor/pluginsmainHEAD0452e08a314c03621ec5ac1324f1ad1dd824f1a4; no releases/tags. Source: X/@cursor_ai, 2026-05-07; Source: Cursor Marketplace, 2026-06-30 - 2026-05-12 | last30days sample: limited recent evidence, but current discussion clusters around using Cursor SDK to run sub-agent workflows and codebase exploration jobs. Source: last30days "Cursor SDK", 2026-05-12
- 2026-05-11 | Captured in wiki; paired with Security and Review Skills for programmatic agents. Source: User, 2026-05-11
- 2026-05-07 | Official launch tweet from @cursor_ai: "Introducing /orchestrate, a skill that recursively spawns agents to tackle your most ambitious tasks with the Cursor SDK." Internal results: autoresearch on skills cut token use by 20% while improving evals; cold start times on internal backend reduced by 80%. (2,765 likes, 1,515 bookmarks). Source: X/@cursor_ai, 2026-05-07
- 2026-06-13 | Quality remediation: linked to the now-existing Cursor SDK page for SDK mechanics (invocation patterns, local/cloud runtimes) and added a stack-fit section. Source: https://cursor.com/docs/api/sdk/typescript