Head to head · Agent frameworks · October 2026 research run

Cursor Agent SDK vs Terse Durable Actors

Terse Durable Actors scores 69.6 (B) on agent readiness against Cursor Agent SDK's 65.5 (B), and leads in 4 of 7 scored categories. Cursor Agent SDK leads on security & auth and transparency & trust. Both do agent frameworks.

Best agent frameworks and SDKs · All 190 frameworks comparisons

Which one, for what

Cursor Agent SDK B

Best for Teams already on Cursor who want version-controlled agents for pull request review, triage and Slack, with evals in CI and one-command hosting.

Ahead on

  • Security & auth, 68 against 49
  • Transparency & trust, 71 against 53

Watch for

Closed source under Cursor's terms, with no public repository, CI or issue tracker

Terse Durable Actors B

Best for Stateful actors for chat, collaboration and multi-agent coordination, as an open-source alternative to Cloudflare Durable Objects per its README.

Ahead on

  • Reliability, 51 against 45
  • Agent ergonomics, 89 against 80
  • Payments & pricing, 90 against 45
  • Maintenance & community, 83 against 74

Also in its favour

  • Free to start without a card
  • Open source

Watch for

Version 0.18.7, with no stable release and no changelog file in the repository

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Terse Durable Actors +45

Cursor Agent SDK 45

Framework reading of the published rubric. No payment protocol (0). Per-million-token prices for Cursor models, including the default Grok 4.5 with Fast, and plan prices are public, but no price for managed hosting and no statement of which plans cover the Agent SDK were found (15). The package is free and the Free plan needs no card, but its usage is only described as limited agent requests (15). A person signs in through a browser or creates an API key in the dashboard before a model turn runs (0). 0+15+15+0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Terse Durable Actors 90

Read with the self-hosted rule, with the price line for Terse Cloud. No x402, MPP or L402 in the repository (0). Terse Cloud publishes per-second prices without a login, US$0.00001971 per CPU and US$0.00000667 per GiB of memory requested (30). The MIT runtime is free to run with no card (30). An agent can start the runtime locally with no signup (30). Total 90.

Security & auth Cursor Agent SDK +19

Cursor Agent SDK 68

Framework reading. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt injection, 15 for audit and 20 for the security programme. Every model turn goes through Cursor's backend with a Cursor credential, even on a self-hosted server, and the data-use page says Cursor may store and train on prompts and code with Privacy Mode off. Managed hosting stores the repository and agent data whatever the Privacy Mode setting. OpenTelemetry export is off until an endpoint is set, with prompt text and tool payloads behind separate flags, and the npm update check has a documented switch. Install copies skills into ~/.cursor/skills (18). needsApproval parks a tool call for a person, dry runs stub writes and the harness tools take an allowlist, but local.sandbox is off by default, so shell commands auto-approve with the host's environment and file tools reach any path the process can. Hosted deployments enforce an egress allowlist (12). The docs tell you to turn the sandbox on for webhook payloads, diffs and chat, document HMAC and shared-secret auth on webhook routes, and warn that anyone who can talk to the agent can drive Cursor account connectors. The scaffolded memory journal shares turns across sessions, with an instruction to treat it as untrusted (10). Sessions keep every message and tool call, hooks can mirror them for audit, and ctx.approvedBy records the approver (14). security.txt and SECURITY.md with a disclosure address and Cursor's GitHub advisories, no bug bounty found, and no advisory for the three package names in OSV on 2 November (14). SOC 2 and ISO 27001 aren't scored on the framework reading. 18+12+10+14+14 = 68.

Terse Durable Actors 49

One server secret, DURABLE_ACTORS_SECRET, as a bearer token for the API and MCP, plus an optional invoke-only key limited to public actor methods. With the secret unset the API is unauthenticated, which SECURITY.md warns about (15 of 30). The invoke-only key and the MCP read-only hints give some least privilege, with no confirmation step before invoke_actor (10 of 20). The OpenAPI file marks actor output as untrusted and to be rendered as plain text, with no guidance for agents on injected instructions (6 of 15). Request history, actor logs, WebSocket sessions and state versions tied to the request that saved them (12 of 15). SECURITY.md gives a private reporting address, security@useterse.ai. No bug bounty, certification or published advisories found (6 of 20). On GKE the self-hosting guide runs actors in gVisor sandbox pods with per-actor storage credentials. Total 49.

Transparency & trust Cursor Agent SDK +18

Cursor Agent SDK 71

Closed source. LICENSE.md reads All rights reserved, with use under Cursor's Terms of Service of 3 September 2026 (15). The data-use page says Privacy Mode keeps Customer Data out of training with zero-retention agreements at model providers, and that with it off Cursor may store and train on code and prompts. The deployment page says managed hosting stores the repository and agent data the same way under Privacy Mode and refuses Privacy Mode (Legacy). No retention periods are stated, and subprocessors are on a trust portal (14). No deprecation policy. The early-alpha migration guide, the persistent removal and the semantic-search removal are documented with error messages but only the changelog entry carries a date (6). OpenTelemetry and the update check are documented with switches. What the Cursor backend logs from turns is covered only by the data-use page (14). 15+14+6+14 = 49.

Terse Durable Actors 53

MIT, copyright 2026 Terse (30). Self-hosted state stays in your PostgreSQL database and GCS bucket per the self-hosting guide. Terse's terms and privacy policy, both dated 14 May 2026, describe an earlier product of flows and workspaces, give no retention periods and don't mention Terse Cloud (10 of 30). No deprecation policy found, and SECURITY.md says older releases get no backports (0 of 20). SDK invocation telemetry is off by default and writes to standard error when enabled, and request spans and platform events are exported only to a collector the operator configures. No call to Terse's own hosts was found in the runtime or SDK source (18 of 20). Total 58.

Agent ergonomics Terse Durable Actors +9

Cursor Agent SDK 80

Framework reading, scored on what it takes to run a tool-calling agent with MCP. One file per tool and one file per MCP connection, tools and disallowedTools filters with effects: "read", and an allowlist for the harness's built-in tools (22). Concurrency caps with queued turns, --fields, page tokens and limits on list commands, and a per-session cost view. We found no turn cap or spend cap for a run (12). Built-in routes return { ok: false, error } codes, direct tool calls have documented 400, 404, 409 and 500 codes, and the CLI has seven exit codes (18). Reads and idempotent calls retry up to three times, writes run once, MCP readOnlyHint and idempotentHint decide retries for connection tools, and dry-run sessions stub writes (20). agent-sdk init scaffolds a working project and every agent field is optional, but the framework is TypeScript only (8). 22+12+18+20+8 = 80.

Terse Durable Actors 89

Ten MCP tools with one-line descriptions (25). Cursor paging with stated limits (1 to 100, or 1 to 500 for requests) and filters by actor, outcome, log level, text and time window (20). Errors carry a code and a message, start limits return named codes with Retry-After, and invalid MCP input says which characters are allowed (14 of 20). Nine tools carry readOnlyHint and invoke_actor carries destructiveHint, but invocations have no idempotency key (15 of 20). Local development needs one command and no credential, with official TypeScript and Python SDKs and generated typed clients (15). Total 89.

Maintenance & community Terse Durable Actors +9

Cursor Agent SDK 74

0.3.0 on npm on 25 October 2026, per the 27 October check (npm not re-read on 2 November), and the docs changelog still ends at 0.3.0 of 23 October (30). Five @grok/agent-sdk versions from 22 to 25 October and 29 @cursor/bdk versions since 22 September, per the 27 October check (20). Closed product. A public changelog with two entries and a forum with no Agent SDK tag, so we couldn't see replies to SDK reports (8). The npm package is current and official, TypeScript only (12). Dependencies are current releases, but there's no public CI and the same build goes out under three names with a postinstall script (4). 30+20+8+12+4 = 74.

Terse Durable Actors 83

v0.18.7 tagged on 18 November 2026, the day of the check (30). 118 tags since v0.1.0 on 2 September 2026, with eight between 15 and 18 November (20). 23 open issues, three of them with long threads (7, 9 and 15 replies) and most with none. Pull requests from five outside contributors were merged between 2 October and 3 November 2026, and CONTRIBUTING.md says GitHub issues are triaged into the team's tracker (10 of 25). Current official TypeScript and Python SDKs at 0.18.7. The MCP endpoint is self-hosted and not in the official registry, which was not searched (15). CI with pinned action versions and lockfiles for Bun, Cargo and uv (8 of 10). Total 83.

Reliability Terse Durable Actors +6

Cursor Agent SDK 45

Local-package reading, since the owner runs the framework, with Cursor's hosting as an option. Official npm package with Node 22.13 or newer stated in engines and in the docs, which also say never Bun (20). Closed source, so no public CI or test suite (0). No public issue tracker. github.com/cursor/cursor holds a README and SECURITY.md, and forum.cursor.com has no Agent SDK tag, so there's nothing to count open crashes against. The troubleshooting page lists known failures with fixes (5). A dated changelog of two entries, 0.2.29 and 0.3.0, both 23 October 2026, and 0.3.0 calls out the removed persistent option, but the 27 earlier @cursor/bdk versions and 123 @cursor/july versions have no notes, and one build ships under three package names (5). Version 0.3.0, but the changelog post of 20 October says generally available and the docs changelog labels 0.3.0 the GA release, which we read as declared stable (15). 20+0+5+5+15 = 45.

Terse Durable Actors 51

Graded as local software, the runtime and SDKs you run yourself. The README and the Python SDK README install with bunx durable-actors or uvx --from 'durable-actors[cli]' and state Bun 1.4.2+ and Python 3.11+, and the release workflow publishes to npm. The registry pages were not read (15 of 20). A public CI workflow runs Rust, Python, TypeScript and example builds on every push and pull request. Whether it passes on main was not checked (15 of 25). 23 issues were open on 18 November 2026, mostly improvements and feature requests, with a few bug reports such as a constructor that keeps its SQLite writes after throwing (17 November) and alarms that run more than once (11 November) (18 of 25). Release notes are generated from pull-request labels on GitHub Releases, which were not read, and no changelog file or breaking-change notes were found in the repository (3 of 15). Version 0.18.7, not 1.0 or declared stable (0). Total 51.

Score by category

CategoryWeightCursor Agent SDKTerse Durable ActorsEdge
Reliability16%4551Terse Durable Actors +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8281Cursor Agent SDK +1
Agent ergonomics13%8089Terse Durable Actors +9
Security & auth14%6849Cursor Agent SDK +19
Payments & pricing10%4590Terse Durable Actors +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7483Terse Durable Actors +9
Transparency & trust7%7153Cursor Agent SDK +18
Negative events≤1500
TotalB 65.5/100B 69.6/100

Facts side by side

FactCursor Agent SDKTerse Durable Actors
KindAgent frameworkAgent framework
VendorCursorTerse
Hosted endpointno (local only)no (local only)
TransportsStreamable HTTP
AuthOAuth or keyAPI key
PricingYour planFreemium
x402nono
LicenceProprietary. The package's LICENSE.md reads "© Anysphere Inc. All rights reserved", with use subject to Cursor's Terms of Service (updated 3 September 2026). No source repository is publishedMIT
Tools exposednone10
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-252026-11-18
Terms last updated2026-09-032026-05-14
Privacy policy last updated2026-09-292026-05-14
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularitynone368 stars

How the scores have moved

Verdicts

Cursor Agent SDK

An agent-as-code framework with typed tools, declared read and write effects that drive retries and dry runs, an approval gate per tool and evals that assert on tool calls. It's closed source, every model turn runs through Cursor's backend on a Cursor plan, local sandboxing is off by default, and the changelog has two entries.

Terse Durable Actors

Durable Actors gives coding agents ten compact MCP tools with read-only and destructive hints, a public OpenAPI 3.1 file and typed TypeScript and Python clients, under MIT with near-daily releases. It is pre-1.0 at 0.18.7, one server secret controls everything unless an invoke-only key is added, and Terse's policies predate Terse Cloud.

Before you call either

Cursor Agent SDK

  1. Install @grok/agent-sdk, not @cursor/agent-sdk from the launch post. That name answers 404 on npm
  2. Set local.sandbox before a turn reads webhook payloads, pull request diffs or chat. Without it shell commands auto-approve with the host's credentials
  3. Give every tool an effect. A tool without one counts as a write, runs once and is stubbed in dry runs
  4. Start agent-sdk serve with --bearer-token on any shared host. --allow-anonymous admits every caller as one principal
  5. Delete bot/hooks/memory.ts when sessions serve different people. The journal shares each turn's message and result with later turns

Terse Durable Actors

  1. Call list_projects first and pass its projectId to every other tool
  2. Never retry invoke_actor when the outcome is unknown, because calls are not deduplicated and run real code
  3. Set DURABLE_ACTORS_SECRET before exposing a server beyond localhost, and send it as a bearer token
  4. Give backends that only call actors the invoke-only key, not the server secret
  5. On 429 actor_start_rate_limited, wait for the Retry-After seconds before starting another actor

Questions

Which is better for AI agents, Cursor Agent SDK or Terse Durable Actors?

Terse Durable Actors scores 69.6 (B) on agent readiness against Cursor Agent SDK's 65.5 (B), and leads in 4 of 7 scored categories. Cursor Agent SDK leads on security & auth and transparency & trust.

Are Cursor Agent SDK and Terse Durable Actors open source?

No open-source release is listed for Cursor Agent SDK. Terse Durable Actors is open source (MIT).

Other comparisons with Cursor Agent SDK or Terse Durable Actors

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.