We're introducing Claude for Teachers: free access to premium Claude capabilities for verified K-12 educators in the US, with a library of teaching skills and a direct connection to evidence-based curricula, mapped to academic standards in all 50 states. https://claude.com/solutions/teachers

Artifacts now support public sharing and multiplayer editing in Claude Code, and can be created with Claude Tag.

The values Claude expresses also vary with the language of the conversation, most noticeably along the Warmth vs. Rigor axis. Claude leans most toward warmth in Hindi and Arabic. In Russian, it leans toward rigor—often asking the user for supporting evidence.

While the differences between models are modest overall, we find that each Claude model sits at a different point along these value axes. Sonnet 4.6, for example, is more playful and affirming, while Opus 4.7 is more likely to give candid critiques.

Because it’s hard to spot patterns by comparing 3,000 values at a time, we clustered similar values together, then identified four key axes along which Claude’s values differ between models: Deference vs. Caution, Warmth vs. Rigor, Depth vs. Brevity, and Candor vs. Execution.

Claude Code on desktop now has an in-app browser. Claude can pull up docs, designs, or any other site. It can read, click through, and interact the same way it does with your local dev servers. It's sandboxed and configurable: you choose whether sessions persist.

A second strategy: use Fable 5 as an orchestrator. Fable 5 plans and delegates to workers (Sonnet 5). Most tokens are billed at the lower worker rate.

On BrowseComp, we tested Claude Managed Agents w/ Fable 5 orchestrator + Sonnet 5 worker sub-agents. The Fable 5 orchestrator achieves 96% of Fable 5 performance at 46% of the price. Token-heavy research is delegated to Sonnet 5. (1/2)

On SWE-bench Pro, Sonnet 5 + a Fable 5 advisor tool gets ~92% of Fable 5's score at ~63% of the price. Fable 5 is called rarely (~once) per task to steer while Sonnet 5 executors the majority of the work. (1/2)

A few patterns we frequently use with Fable 5: Use Fable 5 as an "advisor." An executor (Sonnet 5) calls Fable 5 for guidance. Most tokens are billed at the lower executor rate.

6 months of Claude Max 20x, on us. We're expanding Claude for Open Source to more of the community. If you're a maintainer, a core contributor, someone landing PRs across the ecosystem, or someone keeping a critical package alive, apply today!

/radio 🍓☀️

Advancement through rate limit tiers is automatic. To manually request a higher rate limit, click "Request rate limit increase" in the Claude Console.

We've raised Claude Platform API rate limits for all users and simplified the tiers, which are no longer based on API spend. The latest Sonnet and Haiku models now provide 5x higher rate limits at the highest tier.

Artifacts in Claude Code are now also available on Pro and Max plans. Ask for an artifact, Claude writes the code, publishes it live to claude.a‍i, and updates it in real time while it keeps working. Pages are private to your account and fully self-contained.

Finally, we've added a new Managed Agents Observability tab in Console. This provides session-level metrics such as input/output token use and tool usage.

Agent Overrides let you start a session from a stored agent and override parts of its config for that one session: swap out the model, system prompt, tools, mcp_servers, or skills.

We’ve added a few updates to Claude Managed Agents: Streaming session event deltas, per-session agent overrides, new webhook event types, reverse pagination, and credential injection scoping.

Sonnet 5 provides big gains over 4.6 across reasoning, tool use, coding, and knowledge work. It's built for real engineering work. Navigating large codebases, landing multi-file changes, and carrying long debugging or refactor tasks through to completion.

Claude Desktop is now available on Linux (Ubuntu and Debian) in beta. Alongside the browser and terminal, you now get a first-class desktop experience with Claude Code, Claude Cowork, and chat on all paid plans.

You can now run Claude models in Microsoft Foundry, hosted on Azure. Claude Opus 4.8 and Claude Haiku 4.5 are available through the Messages API with capabilities like prompt caching, thinking, and more. https://x.com/claudeai/status/2071653958905467027?s=20

All of this leans on verification, the single most important thing when agents are used and the place most companies underinvest Spotify rebuilt their test automation around it so engineers can confidently guide and supervise agents, rather than manually execute repetitive tasks

Niklas keeps 5 to 10 Claude sessions running in tmux, one per git worktree, agents working in the background. All of it inside a 20M+ line monorepo. He expected agents to struggle at that size, but it's worked well.

When Claude is working in a channel with four people, whose credentials does it use? The answer: its own. When tagging Claude, Claude gets provisioned like any other teammate, with its own credentials. We call this access model "agent identity". Here's how it works: 🧵

Watching launches and metrics for you Point Claude at an A/B test with the metric and guardrails. It flags when a guardrail moves, your team corrects it mid-run, and it pings when the result is significant with the rollout PR ready.

Background watchers Give Claude a threshold instead of a dashboard, such as pinging when CI stays red too long. It stays quiet until the threshold is crossed, then posts with the failing test and culprit commit already attached. Tell it to put up the fix from the same thread.

Turn a thread into a postmortem When an incident wraps, tag Claude to write it up. It reads the thread back, rebuilds the timeline, drops the postmortem in your docs, and files the action items as issues.

Dependent work Hand Claude the work that's blocked on something else, for example wiring up the frontend once the backend ships to prod. It waits, watches, and shows up days later with the PR, adjusted for whatever changed in review.

Bug triage Let Claude sit in your feedback channel and automatically pick up reports. It finds the code path, reproduces, git-blames, writes a fix, and tags the owner. All that’s left is code review before Claude merges the PR.

Incident response Tag Claude in the incident thread when the page lands. It pulls graphs, diffs the deploy, comes back with root cause and the author tagged. Your team approves in-thread. Claude opens the fix, lands it, watches the metric recover, and resolves the page.