The agent-as-a-service era just started

Cursor dropped a TypeScript SDK on April 29. @cursor/sdk on npm. Programmatic access to their agent runtime. Not a plugin. A full platform.

Here’s the deal. You install it, you get a coding agent you can spin up from CI pipelines, backend services, customer-facing apps. Each one gets its own sandboxed cloud VM. Repo clone. MCP server support. Subagents. Hooks. The whole Cursor harness, except now you’re controlling it from code instead of clicking around in an editor.

That’s not nothing.

The GitHub cookbook hit 2,174 stars in three days. Four starter projects. Minimal quickstart, web prototyping tool, coding agent CLI, and the one that matters: a kanban board that opens PRs when you drag a card.

A non-technical PM drags a card. Types what they want. Wakes up to a pull request. They never touch Git. They never write code. They just describe what they want and watch it appear in the repo.

That’s the product. Not the SDK itself. The cookbook example. A complete workflow for non-technical users getting code merged without touching a terminal. You can build that for clients in a week. Charge for the build. Then charge monthly for the subscription. Different conversation than “I need five Cursor seats.”

Cloud execution is what makes this practical. Every agent gets a dedicated VM. Strong sandboxing. The agent keeps running even when your machine goes offline. Reconnect later, stream the conversation. Long-running autonomous tasks without babysitting a terminal. That’s the gap between “demo” and “something you can actually sell to a client.

The self-hosted angle nobody’s covering

SDK supports three modes. Local, cloud, self-hosted. Most people skim right past self-hosted. Don’t.

Healthcare companies can’t send patient data to third-party clouds. Financial services can’t put trading algorithms on external VMs. Government contractors can’t send anything external. These industries have been locked out of AI coding tools because they can’t comply with data residency. Self-hosted changes that. Your client’s code never leaves their network. You get the engagement. They get the compliance.

Most agencies won’t bother. More work. Requires understanding client infrastructure. Dealing with security teams. But the agencies that do will win enterprise contracts that everyone else can’t touch. Regulated industries are waiting for someone to solve this problem. Self-hosted is the solution.

Nine seconds

DevToolPicks caught something. Cursor released this SDK two days after an agent allegedly wiped a production database in nine seconds. Bold or tone-deaf. Dealers choice.

Cursor knows what their agents can do. They built sandboxing, repo clones, dedicated VMs for a reason. Agents that can write code can delete code. Nine seconds is all it takes.

For operators building on the SDK, remember this. Sandbox everything. Test carefully. Never give an agent write access to production without knowing exactly what it will do.

What you do now

Three steps. No enum, just read it.

Go look at the cookbook repo. The kanban-to-PR example is your blueprint. Clone it, make it work for one client. That’s your proof of concept. A non-technical PM dragging a card and getting a PR is a demo that sells itself.

Think about existing clients. Which workflows could be automated this way? Support tickets to PRs. Documentation updates from Trello. Database migrations from Jira. Pick one workflow. Build it. Charge for the build, then charge for the subscription.

If you serve regulated industries, study self-hosted. Healthcare, finance, government. These clients have been waiting for someone to solve the compliance problem. Self-hosted AI coding agents are the answer. Not many people are offering this yet. The ones who do will have a real advantage.

The era started April 29. What you build with it is up to you.