Verified, then logged.
Sun 22 Nov 2026 · 00:20 KST / 15:20 UTC한국어 | ENSearch /

Breaking02 / IT

Cursor makes its Agent SDK generally available to developers

Bots defined as code folders can be evaluated and deployed to Cursor or a user's own infrastructure, but the changelog omits the licence and deployment pricing.

Seen past an out-of-focus developer, a laptop displays a blurred folder tree beside a monitor of green and amber test-result bars, with a small server on a shelf behind them. AI-generated image

Cursor announced the general availability of its Agent SDK on 20 Oct 2026, giving agent development teams a way to define bots as code folders and carry them through evaluation and deployment.

Cursor's changelog describes the structure with the line "An agent is a project." The file instructions.md serves as the prompt. Each file in tools/ becomes one action the model can call.

Cursor named events from GitHub, GitLab and Bitbucket as triggers for a bot. Slack mentions, scheduled runs and webhooks, automated messages sent from one system to another when an event occurs, also wake it. GitHub events arrive through the user's Cursor account, with no public webhook URL required.

The evaluation feature sends a fixed message to a bot, according to the company. It then checks which tools ran, what inputs they received and the shape of the reply. The agent-sdk github replay command turns a real pull request into signed webhook payloads and sends them to the bot.

Compatibility. Cursor announced the SDK as generally available, and its changelog lists no breaking changes.

Where it runs. The agent-sdk dev command starts a bot locally. The agent-sdk deploy command runs it on Cursor's infrastructure. Cursor said bots can also be deployed to a user's own infrastructure.

The changelog does not give a release version number, a licence or deployment pricing.