Cursor Introduces a TypeScript SDK for Constructing Programmatic Coding Brokers With Sandboxed Cloud VMs, Subagents, Hooks, and Token-Primarily based Pricing

Cursor, the AI-powered code editor, is opening up the core know-how behind its coding brokers to builders in every single place. The Cursor workforce introduced the general public beta of the Cursor SDK — a TypeScript library that provides engineers programmatic entry to the identical runtime, harness, and fashions that energy Cursor’s desktop app, CLI, and internet interface.

This alerts a significant shift in how AI coding instruments are being positioned: not simply as interactive assistants sitting alongside a developer, however as deployable infrastructure that organizations can wire into their present programs.

From Interactive Device to Programmable Infrastructure

If you happen to’ve used Cursor earlier than, you recognize it as an IDE the place you work together with an agent in actual time — asking it to put in writing features, repair bugs, or clarify code. The Cursor SDK adjustments the entry mannequin. As an alternative of a developer sitting at a keyboard, the agent can now be invoked programmatically: from a CI/CD pipeline set off, a backend service, or embedded straight inside one other product.

Consider it this fashion: beforehand, you needed to be “in” Cursor to make use of its brokers. Now, you may name those self same brokers from wherever in your stack with a couple of strains of TypeScript.

Getting began is a single command:

From there, you create an Agent occasion, ship it a job, and stream the response again — all in TypeScript. Right here’s the minimal instance from Cursor’s announcement:

import { Agent } from "@cursor/sdk";

const agent = await Agent.create({
  apiKey: course of.env.CURSOR_API_KEY!,
  mannequin: { id: "composer-2" },
  native: { cwd: course of.cwd() },
});

const run = await agent.ship("Summarize what this repository does");

for await (const occasion of run.stream()) {
  console.log(occasion);
}

The Agent.create() name accepts an apiKey, a mannequin discipline (the place you specify which mannequin to run), and both a native or cloud configuration relying on the place you need execution to occur.

Why Constructing Your Personal Agent Stack is Laborious

Earlier than diving into what the SDK presents, it’s price understanding the issue it solves. Constructing quick, dependable, and succesful coding brokers that run safely in opposition to your information requires significant engineering effort: safe sandboxing, sturdy state and session administration, atmosphere setup, and context administration. And when a brand new mannequin ships, dev groups usually have to transform their agent loops totally simply to benefit from it. The Cursor SDK eliminates this complexity so groups can concentrate on constructing helpful brokers as an alternative of sustaining the underlying infrastructure.

The Agent Harness: What “Similar Runtime” Truly Means

SDK brokers use the identical harness that powers Cursor’s personal merchandise. ‘Harness’ right here refers back to the full set of supporting infrastructure that makes an agent efficient past simply the LLM name itself. In Cursor’s case, that features:

Clever context administration — Codebase indexing, semantic search, and on the spot grep so brokers retrieve the fitting code context earlier than producing responses. That is essential as a result of LLMs are solely pretty much as good because the context they obtain; poor retrieval results in hallucinated or irrelevant outputs.

MCP servers — Brokers launched by means of the SDK can connect with exterior instruments and information sources over stdio or HTTP, both through a .cursor/mcp.json config file or handed inline within the API name. MCP (Mannequin Context Protocol) is an open customary for wiring instruments into agent runtimes.

Expertise — Brokers routinely choose up reusable conduct definitions from a .cursor/expertise/ listing within the repository.

Hooks — A .cursor/hooks.json file helps you to observe, management, and lengthen the agent loop throughout cloud, self-hosted, and native runtimes — helpful for logging, guardrails, or customized orchestration.

Subagents — The principle agent can delegate subtasks to named subagents with their very own prompts and fashions through the Agent software, enabling multi-agent workflows with out customized orchestration code.

Cloud Deployment: Persistent, Sandboxed, and Resumable

One of many extra sensible options of the SDK is cloud execution. When configured to run in Cursor’s cloud, every agent will get its personal devoted VM with sturdy sandboxing, a clone of the goal repository, and a totally configured improvement atmosphere. Critically, the agent retains working even when the initiating machine goes offline — the developer can reconnect and stream the dialog later.

Cloud brokers combine with Cursor’s present Brokers Window and internet app, so a job began programmatically through the SDK may be inspected or taken over manually contained in the Cursor interface. When the agent finishes, it will possibly open a PR, push a department, or connect demos and screenshots — making them appropriate for asynchronous, unattended workflows:

const agent = await Agent.create({
  apiKey: course of.env.CURSOR_API_KEY!,
  mannequin: { id: "gpt-5.5" },
  cloud: {
    repos: [{ url: "https://github.com/cursor/cookbook", startingRef: "main" }],
    autoCreatePR: true,
  },
});

const run = await agent.ship("Repair the auth token expiry bug");
console.log(`Began ${run.id}`);

// ...test again in later, from wherever:
const end result = await (
  await Agent.getRun(run.id, { runtime: "cloud", agentId: run.agentId })
).wait();
console.log(end result.git?.branches[0]?.prUrl);

For dev groups with safety necessities, the SDK additionally helps self-hosted employees, the place each code and gear execution stay contained in the group’s personal community.

Mannequin Flexibility and Composer 2

The SDK exposes each mannequin supported in Cursor. Switching fashions is a single discipline change within the mannequin parameter, letting groups route duties to the very best mannequin for a given mixture of value and functionality. Cursor’s personal Composer 2 — described as a specialised coding mannequin reaching frontier-level efficiency at a fraction of the price of general-purpose fashions — is positioned because the default advice for many coding agent duties.

Getting Began

To speed up adoption, Cursor has printed a public cookbook repository on GitHub with 4 starter tasks: a minimal quickstart (a Node.js instance that creates a neighborhood agent, sends one immediate, and streams the response), a web-based prototyping software for scaffolding new tasks in a sandboxed cloud atmosphere, an agent-powered kanban board that routinely opens PRs when engineers drag a card, and a light-weight coding agent CLI for spawning Cursor brokers from the terminal.

Cursor has additionally launched a Cursor SDK plugin within the Cursor Market to assist builders begin constructing straight from inside the editor.

Key Takeaways

• Cursor SDK is now in public beta — Cursor has launched a TypeScript SDK (npm set up @cursor/sdk) that provides builders programmatic entry to the identical runtime, harness, and fashions that energy the Cursor desktop app, CLI, and internet interface.
• Eliminates the onerous elements of constructing coding brokers — Groups not have to engineer safe sandboxing, sturdy state and session administration, atmosphere setup, and context administration from scratch — and received’t want to transform agent loops each time a brand new mannequin ships.
• Runs regionally or on Cursor’s cloud — Brokers can execute on a developer’s native machine for quick iteration, on Cursor’s cloud in opposition to a devoted VM with sturdy sandboxing, or on self-hosted employees for groups with strict community safety necessities.
• Full harness included out of the field — SDK brokers inherit Cursor’s full infrastructure: clever context administration (codebase indexing, semantic search, on the spot grep), MCP server help, Expertise, Hooks, and Subagents — the identical stack powering Cursor’s personal merchandise.

Take a look at the Cookbook and Technical details. Additionally, be at liberty to observe us on Twitter and don’t neglect to affix our 130k+ ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well.

Must accomplice with us for selling your GitHub Repo OR Hugging Face Web page OR Product Launch OR Webinar and so forth.? Connect with us