Agents defined in code
Cursor’s 20 October changelog announces general availability of Agent SDK. The current overview describes a project of Markdown and TypeScript, with instructions and evaluations kept in version control, running on managed or customer infrastructure. This is a separate setup from choosing a model inside the editor.
Use the current setup reference
The launch entry shows @cursor/agent-sdk, while the current overview names @grok/agent-sdk and says it previously used @cursor/bdk. We have not installed either package. Treat this mismatch as a reason to consult the current official instructions, not to copy an old command from a news post.
Opening is different from deploying
The access reference separates Viewer, Editor and Owner. Viewer opens a bot; Editor deploys, stops and restarts it; Owner also manages secrets and access. A new deployment assigns ownership to its human deployer. With a service-account deployment, the documented owner is the person who created that account.
Before a team rollout, record who can view, deploy and grant access; who owns the service account; and who can stop the agent. Review that record with the intended owner. This is a planning worksheet, not a tested security assessment.
See the new SDK profile and the separate Cursor subscription notes. We have not established a standalone SDK price, free allowance or total hosting cost.
Sources and scope
Provider claims are attributed. Worksheets below or above are proposed checks, not executed workflows. No paid provider, installation, account action or email send was used for this report.