# Cursor — Agent SDK

- Company: Cursor (cursor.com)
- Announced: 2026-10-20
- Category: developer-tool-release
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://cursor.com/changelog/agent-sdk
- Record: https://forck.live/items/27945-agent-sdk
- Subject: Cursor

Cursor released the Agent SDK, a tool that lets developers define an agent as a folder of code, test it with evals, and deploy it to Cursor or their own infrastructure. Agents are projects: instructions.md holds the prompt, each file in tools/ is a typed action the model can call, skills/ holds procedures loaded on demand, mcp-connections/ adds tools from MCP servers, and channels/ defines where the bot receives and answers messages. Developers start with npx @cursor/agent-sdk init ./my-bot and agent-sdk dev, and can pass --template to begin from a security reviewer, an owners-policy approver, a PR autofixer, or a Linear or Jira triager. Running agent-sdk deploy from the project directory builds the agent, gives it a URL, and starts it on Cursor's infrastructure, where secrets and integrations are managed from the dashboard. Agents wake on pull request, comment and CI events from GitHub, GitLab and Bitbucket, on Slack mentions and DMs, on webhooks from any provider, and on a cron schedule; GitHub events pull through a Cursor account, so no public webhook URL is required. Each conversation keeps its own session and a record of every message and tool call, and follow-ups on a pull request or Slack thread resume the same session. Evals send a fixed message and assert on which tools ran, with what input, and the shape of the reply, and agent-sdk github replay turns a real pull request into signed webhook payloads for testing.

## Evidence

Verbatim from https://cursor.com/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

---

Record: https://forck.live/items/27945-agent-sdk
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md