Claude Code is Anthropic’s agentic coding tool, and it represents a fundamentally different philosophy from most things in this space. While other tools give you a chat interface or a visual canvas, Claude Code lives in your terminal. It reads your codebase, understands it, and executes multi-step tasks: writing code, running tests, fixing failures, making commits. It operates more like a pair programmer you can leave running than a chatbot you query.

New in June 2026: Claude Fable 5 lands as the new top-class model

On June 9, Anthropic shipped Claude Fable 5 and made it available in Claude Code. It’s a genuine step up on exactly the work Claude Code does: it scores 80.3% on SWE-bench Pro (versus 69.2% for Opus 4.8) — the hard, whole-codebase variant — plus roughly 95% on SWE-bench Verified, with a 1M-token default context window. In practice that means fewer silent mistakes on long multi-file refactors and better reasoning on the gnarly bugs where earlier models stalled.

Two things to know before you lean on it. First, the economics: Fable 5 is included free in Pro, Max, Team, and seat-based Enterprise plans only through June 22 — on June 23 it moves to metered usage credits at API rates ($10 per million input, $50 per million output tokens, roughly double Opus 4.8). Second, this doesn’t change who Claude Code is for. It’s still a terminal tool for developers, not non-coders. But if Claude Code is already in your stack, restart your sessions to pick up Fable 5, and use the free window to test it on a real, hard task before deciding whether the post-June-23 cost is worth it. We break down the implications for builders in our Claude Fable 5 guide. Source: Anthropic, TechCrunch, Simon Willison.

New in June 2026: The pricing reset we predicted arrives on June 15

The plan restructure we’ve been flagging since April is now confirmed and dated. On June 15, Anthropic splits Claude usage into two billing pools. Interactive usage — you typing into Claude.ai, the desktop and mobile apps, Cowork, or Claude Code live in the terminal — stays on your normal subscription limits, unchanged. Programmatic usage — the Agent SDK, the claude -p command, Claude Code in GitHub Actions, and third-party agents built on Claude — moves onto a separate monthly credit pool (roughly $20 on Pro, $100 on Max 5x, $200 on Max 20x), metered at full API list prices with no rollover.

What this means in practice: if you drive Claude Code by hand in the terminal, your day-to-day is unaffected. If you’ve wired Claude Code into CI, scheduled jobs, or autonomous pipelines, that spend is now a visible, capped line item rather than a hidden subsidy on a $20 plan. The change closes an arbitrage where heavy Agent SDK users were drawing several hundred dollars of API-equivalent compute for $20 — so it’s a correction, not a broad price hike on interactive users. If Claude Code is central to an automated workflow, audit what runs without a human before June 15 and budget for the credit cap. Full breakdown in our guide to the June 15 billing change. Source: Codersera, DevToolPicks, Zed.

The non-coder rating here is 2. Not because Claude Code is bad — it’s arguably the most capable agent in this category — but because it was built explicitly for developers. If you’re reading this and you’re not writing code yourself, you can stop here.

New in May 2026: Claude Opus 4.8 ships as the default model

On May 28, Anthropic released Claude Opus 4.8 and made it the default model in Claude Code. It’s a point release on the same $5/$25-per-million rate card as Opus 4.7, so there’s no price change — just a better model under the hood. Two things matter for the work Claude Code actually does. First, the context window moves to 1M tokens by default, so the agent can hold a much larger slice of your codebase before it starts losing the thread on big multi-file tasks. Second, Anthropic reports the model is roughly four times less likely than Opus 4.7 to let a flaw in code it just wrote pass unflagged, and it scores 69.2% on SWE-bench Pro (up from 64.3%) — incremental on paper, but it shows up as fewer silent mistakes on long agentic runs.

Alongside the model, Anthropic shipped Dynamic Workflows for Claude Code (research preview), which lets the agent adjust its plan mid-task rather than committing to a fixed sequence up front, plus effort control so you can dial reasoning up for hard problems or down for speed and rate-limit savings. The same model also rolled out to Cursor and the Claude API the same week, so the upgrade isn’t a Claude Code exclusive.

Nothing here changes the verdict — this is still a terminal tool for developers. But if you’d already adopted Claude Code, the upgrade is free and worth restarting your sessions for. Source: Anthropic, The New Stack, Simon Willison.

New in May 2026: Self-hosted sandboxes and MCP tunnels — Code with Claude London

On May 19, at the Code with Claude London event, Anthropic shipped two new infrastructure features for Claude Managed Agents that matter for any team running agents in a regulated or security-conscious environment.

Self-hosted sandboxes (now in public beta) let tool execution happen on infrastructure you control — your own servers or a managed provider you choose (Cloudflare, Daytona, Modal, and Vercel are all supported). The agent loop that handles orchestration and context management stays on Anthropic’s infrastructure; what moves to your environment is the actual execution of code and tool calls. For teams where data governance requires that sensitive files, packages, or services never leave their own perimeter, this removes the biggest blocker to deploying Claude Managed Agents on real work.

MCP tunnels (research preview) let Managed Agents and the Messages API connect to private MCP servers without exposing them to the public internet. If your company has internal tooling — a proprietary data store, an internal Jira instance, a private API — you can now give Claude agents access to those systems over an encrypted tunnel rather than having to open a public endpoint.

Neither feature is aimed at non-technical founders — both require infrastructure setup and are firmly in developer/DevOps territory. But for any technical co-founder whose development team is evaluating Claude Code for production-grade agentic work, these are the two features that unlock the enterprise deployment conversation. Source: The Decoder, InfoQ.

New in May 2026: Usage limits doubled — SpaceX compute deal closes

On May 6–7, Anthropic announced it has signed a compute agreement with SpaceX to access the Colossus 1 data center in Memphis: more than 300 megawatts of capacity, over 220,000 NVIDIA GPUs, with more potentially following in orbit. That compute is flowing directly into Claude Code’s rate limits.

What changed for users: the five-hour rate limits for Claude Code are now doubled across Pro, Max, Team, and seat-based Enterprise plans. Anthropic has also removed the peak-hour limit reductions for Pro and Max — which means you’re no longer throttled during business hours. API users are seeing even bigger jumps: Tier 1 API users saw a 1500% increase in maximum input tokens per minute and a 900% increase in output tokens per minute for Opus models. These changes are live now and apply automatically — no plan changes required.

For technical founders who’ve been hitting limits mid-session on long agentic runs, this is material. The throttle that cut your Routine short or killed your context mid-refactor is largely gone. The caveat: the underlying economics still don’t add up at $20/mo for heavy usage, and the pricing change we flagged in April is still likely coming. Use the current limits while they hold.

New in May 2026: Code Review and Remote Agents

Also announced at the Code with Claude 2026 developer event (May 6, San Francisco): Claude Code now includes a native built-in Code Review tool that can analyze a PR or diff and return opinionated, structured feedback — not just syntax notes, but logic errors, test coverage gaps, and security concerns surfaced in the same terminal-native interface. This is Anthropic’s direct response to BugBot in Cursor.

Remote Agents extend Claude Code’s reach beyond the laptop: you can now trigger and monitor Claude Code sessions from your phone, with the agent running on Anthropic’s cloud infrastructure (same as Routines from April). If you kicked off a long refactor and stepped away, you no longer need to be at your desk to check progress or intervene. Source: Code with Claude 2026 event coverage.

New in late April 2026: Anthropic owns the monthlong quality decline

On April 23, Anthropic published an engineering postmortem acknowledging that a series of engineering missteps — not user error and not phantom regressions — were behind the widely-reported drop in Claude Code quality between early March and mid-April. Fortune and VentureBeat both ran the story prominently, and the user response on the Anthropic Discord and on X was sharp: a notable number of paid users said they’d cancelled, and a senior AMD AI exec called the tool “unusable for complex engineering tasks” during the worst of the period.

Three changes were responsible. On March 4, Anthropic cut Claude Code’s default reasoning effort from high to medium to reduce latency — Anthropic now says that tradeoff was wrong and reverted it on April 7. On March 26, a caching change meant to clear stale thinking from idle sessions instead cleared it every turn, which is why Claude Code felt forgetful and repetitive for weeks; that bug was patched on April 10. On April 16, a system-prompt instruction was added to cap responses at 25 words between tool calls — it measurably hurt coding output and was reverted on April 20 (in v2.1.116). The API was unaffected throughout; the regressions only hit Claude Code’s product-side defaults.

Two things matter for non-technical founders considering Claude Code today. First, the quality issues are over — if you tried Claude Code in March or early April and bounced, the underlying tool you’re returning to in late April is materially better. Second, Anthropic’s initial communication implied users were largely to blame before the company walked that back. That’s a yellow flag on trust, not a red one, but it’s worth weighing alongside the technical strengths. Vibe coding tools depend on the underlying AI lab being honest about regressions in real time. Anthropic eventually got there; “eventually” is the operative word.

New in April 2026: Opus 4.7, /ultrareview, and task budgets

On April 16, Anthropic shipped Claude Opus 4.7 and rolled it out as the default model in Claude Code. Three changes matter for day-to-day work. First, there’s a new /ultrareview slash command that scans a file for bugs, security issues, and logical gaps in a single pass — useful as the final pre-commit sweep before you push a PR. Second, Opus 4.7 introduces an xhigh (“extra high”) reasoning effort level that sits between high and max, giving you a middle lever when high is underthinking a problem but max is overkill on latency and cost. Third, task budgets graduated from beta: you can now cap token spend on any autonomous run, which matters a lot once Routines are handling production work unattended.

The model itself shows up in long-horizon agentic work. Anthropic’s stated Opus 4.7 improvement is in “systems engineering and complex code reasoning” — the kind of task where Claude Code has to hold multiple files, a test suite, and a desired end state in its head at once. Early reports on the Anthropic Discord and on X describe fewer turns to complete multi-file refactors and a lower false-start rate on hard bugs. If you haven’t bumped a stuck session to xhigh yet, try it — it’s the first reasoning lever in a while that feels genuinely different from “more of the same.”

New in April 2026: Routines and a redesigned desktop app

On April 14, Anthropic shipped two updates that change how Claude Code fits into a real engineering workflow. The first is a full redesign of the Mac and Windows desktop apps: integrated terminal, faster diff viewer, in-app file editor, expanded preview area, and proper multi-session support so you can run several Claude Code instances in parallel without constant app-switching. This is the first time the desktop experience has felt like a primary surface rather than a thin wrapper over the CLI.

The bigger news is Routines, in research preview for Pro, Max, Team, and Enterprise subscribers. A Routine is a saved Claude Code configuration — a prompt, one or more repositories, and a set of connectors — that runs automatically in the cloud instead of on your machine. There are three flavors: Scheduled Routines (cron-like jobs for things like nightly docs-drift scans or backlog triage), API Routines (HTTP endpoints with auth tokens you can hit from Datadog, PagerDuty, or a CI pipeline), and event-driven Routines (trigger on a GitHub webhook, for example). Because Routines run on Anthropic’s web infrastructure, your laptop doesn’t need to be open.

For technical founders and ops-minded engineers, this is the most interesting update Claude Code has shipped in months. It moves the tool from “agent you run in a terminal” to “agent that runs your on-call response, your nightly cleanup, and your triage queue.” The obvious caveat: the more autonomous the agent, the more carefully you need to scope what it can touch. Start with read-only Routines (reports, scans, summaries) before you let one open PRs unattended.

What makes it different

Most AI coding assistants operate in one of two modes: chat-based code generation (you ask, it answers) or IDE-integrated suggestions (Copilot-style autocomplete). Claude Code operates in a third mode: genuine agentic execution. Give it a task — “refactor this authentication module to use JWT” or “find and fix all the broken tests in the payments service” — and it will work through the problem methodically, using tools to read files, run commands, check output, and iterate.

The context window handling is exceptional. Claude Code is built on Claude’s large context window and uses it to hold an accurate model of your entire codebase — not just the file you have open. This makes it markedly better than most alternatives at tasks that require understanding relationships across files and modules.

Terminal-native matters

The decision to ship this as a terminal tool rather than an IDE plugin or web interface was deliberate. It means Claude Code integrates cleanly with any development environment and workflow. It works with your existing version control, your test runners, your build tools. There’s no proprietary layer that interposes between the AI and your actual code.

Pricing reality

The $20/mo Claude Pro subscription gets you access, but heavy usage will hit rate limits. Teams doing serious agentic work will likely need the API-based billing path, which is pay-as-you-go and can add up depending on codebase complexity and task length. Budget accordingly if you’re planning to use this heavily for large codebases.

Pricing uncertainty worth noting (April 21-22)

Between April 21 and April 22, Anthropic quietly removed Claude Code from the Pro plan feature list on its public pricing page for a subset of new signups — The Register and Simon Willison both documented the change while it was live. Anthropic’s head of growth called it “a small test of 2% of new prosumer signups,” and the Pro pricing page was reverted within a day. Existing Pro subscribers were not affected and the official public pricing is still $20/mo for Claude Code access today. But the signal is clear: the token economics on a $20 plan with heavy Claude Code usage don’t work, and some form of plan restructure — higher price, tighter caps, or a separate Claude Code tier — is likely in the next few months. If Claude Code is central to your workflow, assume your effective monthly cost could move up meaningfully by mid-year and plan accordingly.

Limitations

The agent can make mistakes, particularly on large multi-step refactors where early incorrect assumptions compound. It requires human oversight — you should be reviewing diffs before merging, not accepting changes blindly. The terminal interface, while powerful, has a learning curve for developers who haven’t worked with agentic tools before.

Documentation and onboarding materials were still maturing as of this writing. The tool rewards users who invest time understanding its capabilities and limitations; it punishes those who treat it as magic.

Who it’s for

Senior engineers working on complex existing codebases. Technical co-founders who want to move faster on architecture and refactoring work. Any developer comfortable in a terminal who wants a powerful AI agent they can trust with non-trivial tasks.

Verdict

Among developer-focused AI agents, Claude Code is one of the best available. The combination of genuine agentic capability, large context handling, and terminal-native design makes it stand out. But “best developer tool” and “useful for non-technical founders” are different categories — and this firmly only occupies the first one.

Was this helpful?