Cursor Agent SDK vs LangGraph

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.

LangGraph

Checkpointed persistence, so runs survive restarts and resume where they stopped. No MCP client of its own. LangChain's langchain.mcp is in beta.

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

LangGraph

1. Use a persistent checkpointer in production, not the in-memory one
2. Move from langchain-mcp-adapters to langchain.mcp, and expect a LangChainBetaWarning
3. Set LANGGRAPH_CLI_NO_ANALYTICS=1 on build machines
4. Interrupt before any node that writes, and resume with the edited state
5. Keep the checkpoint and SQLite packages current. Each had a high-severity advisory in late 2025