Cursor Blog
Introducing the Agent SDK
- What happened
- Cursor made the Agent SDK behind its own agents, such as Bugbot, generally available. Agents are defined in code, respond to events like pull requests, and deploy to Cursor's infrastructure with agent-sdk deploy.
- Why it matters
- Team-specific review or compliance bots no longer have to be built from scratch or bent to fit someone else's product. Prompts, tools and evals sit in one versioned project, so an agent's behavior can be reviewed and tested like application code, and it can be self-hosted.
- Why you should care · TypeScript
- Tools are TypeScript functions and the agent is configured with a defineAgent call, so your editor, type checker and code review cover the agent the same way they cover the rest of your codebase.
- Try this
- Create a project with defineAgent from @cursor/agent-sdk, write one Markdown prompt that checks pull requests against a single team rule, and test it in the local playground with an eval before using agent-sdk deploy.
Why this is here
- You use TypeScript
- Core to Backend work