Cursor ships Agent SDK, the framework behind Bugbot and Security Reviewer, deployed with one command
- Cursor released the Agent SDK, the framework it uses to build its own managed agents such as Bugbot, Security Reviewer, and Rollouts, and opened it to general availability.
- Agents are laid out like a small software project: prompts in Markdown, tools as TypeScript functions, connections and evals in the same directory, so changes go through normal version control and review.
agent-sdk deploybuilds the agent, gives it a URL, and runs it on Cursor infrastructure with dashboard-managed secrets, while the same agent can also run as a single Node process in a container on your own servers.- An internal Cursor team built kb-reviewer in about a day; it runs on every pull request in their main codebase, flags changes that contradict a recorded lesson, and cites the note behind each finding.
- The SDK ships with evals and event replay out of the box, and agents can hand work to a specialized agent or split a job across parallel subagents; the PGA Tour uses it to power its software development factory.
Hacker News 의견들
I have so many use cases for this, but coupling an app to one vendor really doesn't appeal to me. We need a standard like Open Responses, since OpenAI's Agent API and Anthropic's Agent SDK are basically the same thing already.
I'm starting to think the LLM ecosystem is going the way of JS: endless technologies, almost no adoption. Literally every day there's a new tool and the one from last week is deprecated.
That's the whole point of AI. It's consumerism applied to software, and it sucks.
People spend so much time building workflow skills with zero benchmark proving they beat a plain one sentence prompt.
I'll never understand this argument, especially from hackers. Why is a large number of ideas and frameworks a bad thing?
Gotta justify that $160k salary somehow. If the AI writes the code, your job is managing it, so you fill the day making new tools and markdown files.
The difference is those endless technologies will probably be used by other agents without people's knowledge.
The real shift is from people pushing software to git to agents pushing it somewhere. Software factories are game over for our industry.
OpenAI and Anthropic already have Agent SDK brands, and Vercel has AI SDK. Can someone come up with a new name for a project?
Google has ADK, Agent Development Kit, so the naming ship has fully sailed.
Honest question: why isn't an agent SDK just a PROMPT.md plus a runtime that runs the LLM with tools? Why the langchain style abstractions?
The runtime is the thing you're building. A custom loop lets you scope tools to the user's permissions, which matters for authorization.
Agents aren't at the level where you hand an unconstrained LLM some tools and walk away. You need different models, guardrails and logging per step, plus something you can explain to security and legal.
Why put the vibe back in if you're implementing a specific software process to avoid the vibe?
Why would anyone not use an open source harness in October 2026? Genuinely curious what the alpha is.
Claude Code Max is way cheaper than paying API price, and the frontier harness is tuned to the model. I'd rather wait it out than hop tools every month.
At this point the complex features feel like productivity theater. I type instructions and it spits out code, that's it.
I'd just build my own harness. Gateway, memory, tool calls, LLM API, the basics are simple and then it can improve itself.