cursor

Pick Copilot coding agent when the work starts and ends on GitHub and you want issue-to-PR with native branch protection. Pick Cursor cloud agents when you want a live, editor-attached VM, multi-repo tasks, and to take over the run by hand. Full feature matrix, the 59-minute cap, the Actions-approval gotcha, and June 2026 billing for both.

Commit .cursor/mcp.json for the IDE, register shared servers under Dashboard > Integrations & MCP for cloud agents, and keep secrets out of git with ${env:...}. The full two-surface setup for Cursor 3.11 (July 2026), including why the repo file alone does not reach cloud agents.

Use Cursor 3.8's /automate skill to spin up a cloud agent that fires on GitHub events. Covers the five GitHub triggers added June 18, 2026, tool config, repo scope, and the Max Mode billing gotcha.

Cursor 3.11 (July 10, 2026) adds side chats, durable parallel agent threads you spawn with /side or /btw and pull back into the main conversation with an at-mention. Plus Cmd+K transcript search and new cloud agent hooks.

Cursor 3.11 (July 10, 2026) lets cloud agents run hooks that see the conversation itself. Wire up beforeSubmitPrompt, afterAgentThought, afterAgentResponse, and subagentStart in .cursor/hooks.json to log every prompt, thinking block, and delegated task, then gate the risky ones.

Both let one agent spawn isolated workers from a Markdown file, but Claude Code nests five levels deep with per-agent tool allowlists and worktree isolation, while Cursor keeps it to two levels with a single readonly switch and reads Claude's format for free. Pick by where your agents run, not by brand.

Cato AI Labs disclosed CVE-2026-50548 and CVE-2026-50549, a pair of 9.8 CVSS flaws in Cursor's terminal sandbox. A poisoned MCP response or web result can escape the sandbox and run code. Cursor 3.0 is the fix.

Cursor 3.9 ships a plugin system and a unified Customize page so skills, rules, MCP servers, commands, and hooks travel together as one versioned unit.

Cursor 3.7+ lets you run Bugbot before you push with the /review command. Here is how local review works, how the patch ID dedup stops you paying twice, and the one thing it cannot do yet.

Define named subagents on agents in the Cursor SDK, let a code-reviewer delegate to a test-writer through the built-in Agent tool, and understand the real nesting depth cap: a subagent spawned by another subagent cannot spawn further ones, despite the changelog's 'and so on'.