Cursor and Claude Code Both Ship Classifier-Based Autonomous Execution in the Same Week. The Industry Just Chose Its Architecture.

Within five days of each other, both Claude Code (v2.1.158, May 31) and Cursor (3.6, May 29) shipped remarkably similar architectures for autonomous agent execution. Both use a classifier subagent that reviews each pending action against conversation context and decides: allow, retry, or ask the human. Both use allowlists for known-safe operations. Both sandbox containable actions. Both apply model-based judgment for everything else.

This isn't a coincidence. It's convergence on the only architecture that works.

Claude Code's Auto Mode is now available on AWS Bedrock, Google Vertex, and Microsoft Foundry for Opus 4.7 and 4.8, enabled via CLAUDE_CODE_ENABLE_AUTO_MODE=1. Cursor's Auto-review lets users configure the run mode in Settings > Agents > Run Mode and steer the classifier with custom instructions. Same pattern. Same week.

The problem they're both solving: the binary choice between "approve every action manually" (safe but slow) and "let the agent run free" (fast but terrifying) doesn't match how developers actually want to work. Most actions are fine. Some are risky. The question is: can a model tell the difference?

I've been running Auto Mode since it hit the Anthropic API, and the answer is mostly yes. File reads? Auto-approved. Test runs? Auto-approved. Deleting a production config? It asks. The classifier gets it wrong sometimes (usually by being too conservative), but the productivity gain from not clicking "approve" on every grep command is real.

What matters here isn't the feature. It's that two teams with no coordination built the same thing simultaneously. When that happens, you're looking at a discovered truth about the problem space, not a design choice. Classifier-gated autonomy is the architecture. Expect every other coding agent to ship something equivalent within 90 days.

What builders should do: enable it. Start with conservative settings and let the classifier learn your patterns. If you're building agent tooling yourself, this is the pattern to implement. Full manual approval doesn't scale. Full autonomy isn't trustworthy. The middle ground is a learned classifier.