Maya: Hey builders! Here's what's on the radar today on Claude Code Review. Sonnet five point five undercuts Opus on price, Claude Code's read-only check got bypassed, auto mode became the new default, headless runs burn more limit, and MCP servers stalling on tools. I'm Maya. James: And I'm James. Let's get into it. Maya: Anthropic released Sonnet five point five, and hands-on write-ups tested it against Opus five point five and GPT-6 Astra. On Terminal-Bench four point zero, Sonnet jumps from ten point three percent to seventy point six percent, and it beats Opus there. James: That's the headline number, Maya, but the price is the practical part. Two dollars input, ten dollars output, half of Opus and a fifth of Astra, at the same per-token rate as Sonnet five, plus over thirty percent faster. Maya: Exactly right, and yet the builds lean the other way. Opus won four of five tests where all three had data, and on the hotel landing page and explainer video, the tester still picked Opus over Sonnet. James: Now to a security disclosure. Anthropic disclosed CVE-2025-66032, rated eight point seven High, reported by RyotaK of GMO Flatt Security. Claude Code's read-only validator could be tricked into auto-approving a command that then ran arbitrary code. Maya: The mechanism is sharp, James. The validator matched the surface form instead of parsing what the shell would do. Dollar-sign I-F-S can stand in for a space, plus short flag forms, so a command looked read-only and got approved. James: Right, and Anthropic is clear this is a bypass of the gate, not standalone remote execution. It needs untrusted content in the context window, so it pairs with prompt injection from a malicious file, issue, or tool output the agent reads. Maya: And the fix teaches the lesson. Version one point zero point nine three swapped the blocklist for an allowlist, which refuses anything unfamiliar and fails closed. No in-the-wild exploitation, and auto-update users got it. Anyone pinned older should check they're at one point zero point nine three or later. James: Next, Claude Code v two point one point two eight three made auto mode the built-in starting mode for terminal and VS Code sessions, on every plan and provider. Auto mode uses a classifier to decide which actions are blocked. Maya: So the ritual of pressing Shift-Tab into plan mode is gone, James. And Boris Cherny, who built Claude Code and wrote plan mode, agreed it's fading. Plan mode never changed the toolset, it just added a line telling the model not to write code yet. James: That's the key detail, and swapping toolsets mid-conversation would invalidate the prompt cache anyway. Cherny said with newer models the model just got it, and planning moved into the normal back-and-forth. Claude Code still has all six permission modes. Maya: Though one commenter pushed back, that plan mode still earns its keep when the blast radius is high, like auth, payments or a shared schema, where a human needs a moment to say no before the edit starts. James: Here's a measurement worth budgeting for, James. A six-run Pro-account test on r/ClaudeAI found headless Claude Code, meaning the Python Agent SDK and claude dash p, burned far more of the five-hour limit than interactive VS Code or the terminal CLI. Maya: And that's the surprise, James. Interactive use ran about one point seven percent of the limit per dollar of tokens. Headless ran about five point two percent, roughly three times per token, even though headless used fewer tokens and fewer steps. James: Same commit, fresh worktree, Opus five at medium effort each run. The takeaway: an eighteen-dollar task headless takes about ninety percent of a five-hour window, versus thirty percent interactively. Caveat, six runs, one task, one account. Maya: Last one. Since Claude Code began negotiating the twenty twenty-six oh seven twenty-eight version of MCP, some local servers connect fine and then list zero tools. The new handshake sends a subscriptions-slash-listen request that older Go servers never answer. James: Right, Maya, so tools-slash-list times out after thirty seconds. Watch the logs for Failed to fetch tools, Request timed out. Two workarounds: set MCP underscore PROTOCOL underscore NEGOTIATION to legacy, or grep out the listen request before it reaches the server. Maya: And the permanent fix is updating the server's mcp-go dependency to version one point one point one or newer, then redeploying. The issue names mcp-grafana as affected. If you maintain a Go server, check your version before your users hit this. Maya: That's your Claude Code Review daily brief. Check claudecodereview.ai for the full stories. Keep building.