Build and evaluate a Cursor agent as a code project
Cursor’s Agent SDK launch describes agents as code folders with instructions, tools, skills and channels. The SDK includes a local playground and evaluations, with deployment to Cursor or the developer’s infrastructure.
Source checked November 2, 2026
Listen to this articleAbout 2 min
Preparing audio…
AI narration. Your voice and speed choices stay in this browser.
EDITORIAL TAKEAWAY
Start with one small task and an evaluation that checks the expected result. Review permissions before connecting real services or enabling event triggers.
Before you try it
- Announced generally available October 20. The launch note does not establish a complete plan, region or deployment-pricing matrix.
- Local development and hosted deployment are separate steps. Check current documentation and account requirements before deploying.
- Channels can respond to repository events, Slack, webhooks or schedules; connecting a channel is a separate configuration choice.
A small next step
Our suggested way to explore the change.
- Choose one bounded workflow and start from a suitable SDK template.
- Use the local playground with sample inputs, then add an evaluation for the expected actions and output.
- Inspect tool permissions, secrets and trigger behavior before connecting production services.
Go to the source
Cursor · Agent SDK launch ↗Availability can change. Check the maker's current requirements before making a decision.