AgentOS vs Cursor Agent SDK

AgentOS

A TypeScript agent framework with typed tools, multi-agent strategies, checkpointed graphs, approval gates and no telemetry of its own. It is at 0.14.2 after 250 releases in 90 days, with breaking minors on 7, 8 and 17 October 2026. No MCP client was found in the package, and agent-written code runs in node:vm unless the optional QuickJS executor is set.

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.

AgentOS

1. Pin an exact version of @framers/agentos. Feature commits ship as patch releases while it is 0.x, and breaking changes ship as minors
2. Leave emergentConfig.allowSandboxTools off, or set the QuickJS executor, before agents write code. The default node:vm executor shares the host process
3. Pass your own ICheckpointStore to compile() for runs that must survive a restart. The default store is in memory
4. Set hitl.approvals.beforeTool for tools that write, and choose a handler. No approval gate is on by default
5. Use Node 22 or newer, and set a provider key such as OPENAI_API_KEY or ANTHROPIC_API_KEY. The provider is detected from the environment

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