Cursor launched an Agent SDK for defining, testing, and deploying AI agents as code, with

EXHIBIT 2303 · FLASH

Oct 26, 2026 19:20 UTC docs https://cursor.com/changelog

Cursor launched an Agent SDK for defining, testing, and deploying AI agents as code, with support for various channels and eval methods.

READY TO POST:

cursor just dropped an agent sdk! looks like you can define agents as code, test with evals, and deploy to cursor or your own infra. pretty neat for dev workflows.

the new cursor agent sdk is out, letting you build bots for github, slack, webhooks, and more. it even has templates for security reviewers and pr autofixers.

Cursor changelog changed: https://cursor.com/changelog 104 added lines --- +++ @@ -46,2 +46,54 @@ Changelog +Oct 20, 2026 +· +Changelog +Agent SDK +The Agent SDK is available today. It allows you to define an agent as a folder of code, test it with evals, and deploy it to Cursor or your own infrastructure. +Run +npx @cursor/agent-sdk init ./my-bot +, then +agent-sdk dev +to start the bot locally with a playground. Pass +--template +to start from a security reviewer, an owners-policy approver, a PR autofixer, or a Linear or Jira triager. +# +Deploy agents wherever you need them +When you're ready to put an agent into use, you can deploy it to Cursor by running +agent-sdk deploy +from the project directory. The command builds the agent, gives it a URL, and starts it on our infrastructure. You can manage secrets and integrations from the dashboard, while continuing to use the same logs, evals, and playground available locally. +# +Agents as code +An agent is a project. +instructions.md +is the prompt. Each file in +tools/ +is one typed action the model can call. +skills/ +holds procedures the model loads on demand, +mcp-connections/ +adds tools from MCP servers, and +channels/ +defines where the bot receives and answers messages. +agent-sdk validate +checks the project and +agent-sdk info +prints what was discovered. +# +Channels +Agents wake on pull request, comment, and CI events from GitHub, GitLab, and Bitbucket; on mentions and DMs in Slack; on webhooks from any provider; and on a cron schedule. GitHub events pull through your Cursor account, so no public webhook URL is required. Slack is well-supported out of the box. +Each conversation keeps its own session and a complete record of every message and tool call. Follow-ups on a pull request or Slack thread resume the same session. +# +Evals +An eval sends a fixed message to the bot and asserts on what it did: which tools ran, with what input, and the shape of the reply. Run +agent-sdk eval +locally or in CI. +