Cursor makes its Agent SDK generally available for building and deploying agents

Archive entry: this covers an event from October 20, 2026, and we published it on November 8, 2026. The details come from sources dated at the time and may have changed since.

On October 20, 2026, Cursor made its Agent SDK generally available, as described in a Cursor blog post on the Agent SDK. With the SDK, an agent is a project folder that is tested with evals and deployed either to Cursor or to self-managed infrastructure.

What the Agent SDK offers

• A project was started with npx @cursor/agent-sdk init ./my-bot and run in a local playground with agent-sdk dev.
• --template starters included security review, owners-policy approval, PR autofixing and Linear/Jira triage.
• agent-sdk deploy gave the agent a URL on Cursor's infrastructure.
• Triggers included PR and CI activity on GitHub, GitLab or Bitbucket, Slack mentions and DMs, webhooks and cron schedules.

What it means for people building with AI

Developers could build and ship their own Cursor-powered automation agents, such as PR fixers or triage bots, as code. Evals made it possible to test an agent before deployment, and teams could choose between Cursor's infrastructure and self-managed infrastructure. Triggers ranged from PR and CI activity and Slack mentions to webhooks and cron schedules, so an agent could react to events or run on a timetable.

Where to read more

The Cursor changelog carries an Agent SDK entry dated October 20, 2026, which states that the SDK is generally available as of that date.

Sources

• Introducing the Agent SDK (Cursor, October 20, 2026, official)
• Agent SDK (Cursor, October 20, 2026, official)

Written with AI assistance, strictly from the sources listed above. Before it went live, automated checks verified its dates, sources and every language edition.