Skip to main content

This Month in Claude

All levels

A plain-English digest of what's changed recently across Claude — so you can skim "what's new and what it means for me" without reading every changelog. Newest first.

:::info How this page stays current Entries are added by the community and by an automated watcher that flags upstream changes for a human to write up. Each entry links its official source. See something missing? Add it. :::

How to read an entry​

Each update is tagged by surface — 🗣️ Apps (chat/voice/mobile), 🛠️ Claude Code, 🔌 API, 🧠 Models — and answers "what it means for you."

Recent updates​

  • 🧠 Models — Claude Fable 5.1 (claude-fable-5-1) and Claude Mythos 5.1 (claude-mythos-5-1) shipped September 1, 2026. Same Mythos-class tier above Opus, same 1M context, 128K output, $10 / $50 per MTok, same tokenizer and always-on adaptive thinking as Fable 5, but cache reads dropped from $1.00 to $0.25 per MTok (0.025× base input instead of 0.1×), which is where Anthropic's "about 25% cheaper on typical workloads, up to 45% on highly agentic ones" comes from. Three changes are breaking: tool_choice of type any or tool now returns 400 (keep auto, set strict: true, and name the tool in the prompt); thinking blocks are readable only by Fable 5.1 or newer, so routing a conversation down to Opus 5 silently drops the reasoning unless you send the thinking-binding-controls-2026-08-01 header; and editing anything before a thinking block (system prompt, tools, earlier turns) invalidates later blocks, enforced as a 400 for accounts created on or after August 31, 2026. Five are additive, all beta: per-message effort without a cache miss (mid-conversation-output-config-2026-07-01), turn-scoped system messages via clear_at: "next_user_message" (mid-conversation-system-clear-at-2026-08-21), thinking.display: "updates" to surface progress notes between tool calls (thinking-display-updates-2026-08-18), the cheaper cache read, and a statistical text watermark plus C2PA credentials on generated files. Anthropic's positioning is unchanged: start with Opus 5; use Fable 5.1 when Opus 5 at higher effort still falls short. Now the Claude Code default Fable model (v2.1.257); not on Priority Tier; 30-day retention required. What it means: if you pin claude-fable-5, grep for forced tool_choice and for any code that edits conversation history before flipping the ID. Full migration guide with the seven documented behavior shifts (fewer parallel tool calls, less narration, whole-file rewrites) and Anthropic's launch benchmark table: Claude Fable 5.1: What Changed and How to Migrate.
  • 🧠 Models (cross-AI) — OpenAI's GPT-6 Astra (gpt-6-astra) went GA on September 4, 2026 after a September 3 limited release, ending the five-week "preview with no price" period. Confirmed specs: 1,050,000-token context (922K max input), 128K output, April 30, 2026 cutoff, $10 / $50 per MTok, cached input $1.00, Chat Completions + Responses + Batch (tools need Responses; no Realtime, Assistants, or fine-tuning), reasoning effort low through max, and the GPT-5.6-style 272K cliff (cross it and the whole request is re-priced 2× input / 1.5× output). Independent numbers from Artificial Analysis (September 9): tied with Claude Fable 5.1 at 53 on the Intelligence Index and 62 on the Coding Agent Index, at roughly a third of the output tokens and 40% less cost per task; ahead on Terminal-Bench 4.0 (59% vs 52%); behind GPT-5.6 Sol on GDPval-AA v2. Safety: first OpenAI model at the Critical cyber tier, exploit capability gated behind a vetted-access program, and a system card that says chain-of-thought monitorability decreased versus Sol because the "recurrent depth" architecture moves reasoning inside the model. What it means: Astra and Fable 5.1 are now peers on agentic coding at the same list price, but the bills diverge on long loops (Astra's cache reads are 4× Fable 5.1's) and the benchmarks were run at max effort while the API defaults lower. Full comparison, the four API gotchas, and a per-workload decision table: GPT-6 Astra: The Field Guide for Claude Users.
  • 🛠️ Claude Code — The first two weeks of September (v2.1.257–v2.1.270) shipped a run of practical tooling. /skill-doctor (v2.1.252+, September 4) reports what each loaded skill costs in context per turn, how often it's invoked, and flags never-used skills with instructions for where to turn them off; prune the highest-cost unused ones first (not available over Remote Control). claude plugin eval <plugin> (v2.1.268+, September 11) runs a plugin's eval suite, JSON cases in evals/ or the experimental.evals manifest field, and produces scored, reproducible JSON + HTML reports; claude plugin validate --json --strict turns warnings into CI failures. /diff (v2.1.260) opens a side-by-side panel of uncommitted changes as Claude edits in fullscreen mode. /cost and the status line's prompt_cache field now name the likely cause of a cache miss (tool definitions or system prompt changed, idle past the TTL). For fleets: maxEffortLevel (v2.1.267) caps effort per model on every provider; --permission-prompts none (v2.1.259) auto-denies anything that would prompt on unattended headless hosts; managedMcpServers lets an org push HTTP/SSE MCP servers to every user; bashEditDiffEnabled appends a diff of files a Bash command changed to the tool result; CLAUDE_CODE_WORKFLOW_MAX_CONCURRENT_AGENTS (1–256) raises the Workflow tool's fan-out cap; /output-style [name] now works in headless and Remote Control sessions. What it means: /skill-doctor is the fastest context-budget win available today; run it once per project and delete what it flags. The plugin eval command is the first native way to regression-test a plugin before publishing.
  • 🛠️ Claude Code — A fifth built-in output style, Concise, shipped in v2.1.237 (Week 34, Aug 17–21 2026) — Claude leads with the result, skips preamble and narration, and keeps responses short by default, while doing the engineering work as thoroughly as Default. Ask for detail and it answers in full; error reports, security warnings, and destructive-action confirmations stay complete regardless — Concise never quiets the things you must not miss. Same window also landed force-for-plugin in output-style frontmatter (a plugin can auto-apply its style and override the user's outputStyle setting — use sparingly), and made nested project-level styles resolve closest-directory-wins so a package inside a monorepo can override the workspace default. Styles still don't cross into subagents (each subagent runs its own system prompt), but /fork is the one exception — it copies the parent's full prompt and therefore keeps the style. What it means: if you kept re-prompting for "just the result, no preamble" every session, drop the ceremony and set "outputStyle": "Concise" in ~/.claude/settings.json. Full rewrite with the five-style comparison table, subagent-scope rules, the frontmatter field reference, and a quiz covering all of it: Output Styles.
  • 🔌 API — Anthropic made Claude Sonnet 5's introductory pricing permanent on August 10–11, 2026 — the $2 / $10 per MTok launch price was scheduled to jump to $3 / $15 on September 1, and that increase will not happen. Same model ID (claude-sonnet-5), same 1M context, same 128k output — just no price hike. What it means: budgets, evals, and cost forecasts you built assuming a September price jump can stand down. If you deferred a Sonnet-5 migration because of the impending increase, there's no longer a September cliff to plan around. The Current Models & Pricing page keeps pointing to Anthropic's official pricing page as authoritative — a stale price on our site is worse than none.
  • 🔌 API (cross-AI) — Cloudflare shipped Kitesurf on August 6, 2026 — a stateless, agent-first browser runtime that runs entirely in V8 isolates on Workers, discarding the Chromium engine that has underpinned nearly every headless browser tool for the past decade. Cloudflare's own benchmarks: 3.1× less CPU and 4.7× less memory than Chromium on screenshots, 3.8× less CPU and 7.0× less memory on HTML extraction — traded for about 1.7–1.8× more wall-clock time per task (Boa interprets JS instead of V8-JIT-ing it). Kitesurf speaks the Chrome DevTools Protocol, so Puppeteer, Playwright, chrome-remote-interface, and chrome-devtools-mcp connect unchanged via a single --wsEndpoint swap. Rendering uses Firefox's CSS engine (Stylo) and the Rust Blitz engine — that's how a 12-week-old project already passes 235,000+ Web Platform Test subtests. Free public beta today; open-source release planned. Four things it cannot do yet: video, WebGL, TLS-fingerprint bot-challenge negotiation, persistent authenticated sessions. What it means: the browser stack for agents and the browser stack for humans are diverging into two products. If you run any bursty, short, HTML-shaped browsing workload on per-CPU-second billing, Kitesurf changes the math — see the full practical read at Cloudflare Kitesurf: The First Browser Runtime Built for AI Agents.
  • 🛠️ Claude Code — Auto mode becomes the default permission mode on August 14, 2026 for new sessions on Pro, Max, and Team plans (Week 32 digest, v2.1.220–v2.1.224). Instead of stopping to ask on every non-read action, Claude Code proceeds unless a separate classifier judges the action irreversible, destructive, or aimed outside your environment (curl | bash, force pushes, prod deploys, rm -rf on unresolved variables, transcript tampering, destructive git that discards uncommitted work, secret exfiltration). Anthropic's own justification: in a study of over 1,000 paid users, the auto-mode classifier caught 89% of harmful actions vs 13.6% for manual review — because habituated users approved about 97% of prompts without reading them. Two carve-outs preserve intent: if you already set permissions.defaultMode in your user settings, it stays put unless you accept a one-time in-app switch prompt; if your organization manages the default (Team/Enterprise managed settings), nothing changes automatically. Related change already in effect: classifier calls made by auto mode no longer count against your usage limits. What it means: if you want to keep the old prompting behavior on Aug 14, set "permissions": {"defaultMode": "default"} in ~/.claude/settings.json before then (or "auto" to opt in early). The updated deep-dive — what auto mode blocks, how to opt in / opt out, and how it composes with bypassPermissions and hardened autonomous runs — is at Permissions & Permission Modes.
  • 🛠️ Claude Code — Cross-session messaging shipped in v2.1.224 (Week 32, Aug 3–7, 2026): on macOS and Linux, two open Claude Code sessions on the same machine can now message each other without you being the copy-paste bridge. Claude discovers other sessions with the ListAgents tool and sends with SendMessage, either when you ask ("tell the session working on the payments API that users.name is now users.display_name") or on its own after a change in one session affects what another is doing. The recipient shows a Message from row you expand with Ctrl+O; /list-agents prints the reachable set. What travels is text Claude writes for the other session — not your conversation history or files. What it means: this is Anthropic's first native answer to the interdependent-project pain that community projects (file inbox, WebSocket bus, MCP channels) have been solving for months — see the still-relevant trade-off matrix at Inter-Session Messaging if you need multi-machine, richer artifacts, or debuggable transport.
  • 🧠 Models — Claude Opus 4.1 (claude-opus-4-1-20250805) was retired on August 5, 2026 as scheduled — API calls to that ID now return an error. Recommended replacement is claude-opus-4-8 (or straight to claude-opus-5). What it means: if anything in your codebase, CI, gateway config, .env, or eval harness still pins the Opus 4.1 ID, it's failing right now — grep for claude-opus-4-1 and flip it. The Deprecation & Migration Watch tracks the current retirement schedule; see the Opus 5 field guide for the contract changes to watch when jumping straight to the current flagship (adaptive thinking on by default, sampling knobs return 400, tokenizer counts ~30% more tokens).
  • 🛠️ Claude Code — Sandbox credential masking got teeth across three August releases (v2.1.221 on August 4, v2.1.223 on August 6, v2.1.224 on August 7) — the sandbox proxy can now let gh, npm, aws, and any HTTP client authenticate without the sandboxed command ever holding the real secret. Environment variables (v2.1.199+) and files (v2.1.221+) with "mode": "mask" show the sandboxed process a per-session sentinel; the proxy substitutes the real value on outbound requests to hosts you allow. v2.1.224 landed the meaningful additions: extract to mask one field inside a structured value (e.g. the password inside DATABASE_URL), decode: "jwt" with maskClaims to swap in a structurally valid fake JWT so in-sandbox decoders keep working, and credentials.awsPairs + credentials.sigv4 so the proxy can re-sign SigV4 requests when your AWS credentials live in non-standard variable names. Two gotchas that catch every first integration: network.tlsTerminate is mandatory (without it the sentinel goes over the wire and auth fails), and mask / tlsTerminate / awsPairs / sigv4 are silently ignored from a repo's .claude/settings.json — they only work from user, managed, or --settings scopes (a repo you cloned can't order the proxy to forward your real token). Also that week: VSCode Focus view (Ctrl+Alt+F, v2.1.221) hides tool activity behind an expandable per-turn summary, archive plugin source (v2.1.224) installs plugins from a zip over HTTPS with optional SHA-256 pinning (no git/npm needed), and the 200-subagent-per-session spawn cap was removed (v2.1.224). What it means: the full practitioner's guide — mask vs deny, all four modes with copy-paste JSON, the Linux/WSL vs macOS matrix, the settings-source rule, and a recommended user-settings starter — is at Sandbox Credential Masking: keep tokens working, keep them secret.
  • 🛠️ Claude Code — Self-hosted environments shipped August 7, 2026 in beta (Claude Code v2.1.224) on Team and Enterprise plans — a first-party way to execute Claude Code cloud sessions (web, mobile, desktop, claude --cloud, scheduled routines) on your own hosts while orchestration and inference stay on api.anthropic.com. Three moving parts, same shape as GitHub Actions: an environment (a named destination created on the Cloud environments admin page, ID ccpool_...), one or more runners (long-lived claude self-hosted-runner processes on your Linux or macOS hosts), and sessions (spawned child claude processes that clone the repo and stream events back). Every connection is outbound HTTPS — Anthropic never opens a port into your network. The operational surprise: a runner locks to the first user that lands on it and only serves that user until it drains, so minimum fleet size = concurrent active users, not concurrent sessions. Not available under ZDR; inference can't be routed off Anthropic (no Bedrock, Vertex, Foundry, or LLM gateway); GitHub-only checkouts today; Claude Tag, Claude Security, and Code Review sessions don't route yet. What it means: the full practitioner guide — the four-command quickstart, the --drain-grace-sec / --retire-at lifecycle, the network shape, the production checklist, and the six gotchas (including the show-once environment secret and the 5-minute clock-skew auth failure) — is at Self-Hosted Environments: run cloud sessions on your own boxes.
  • 🔌 API — Managed Agents got four upgrades on August 7, 2026 — the headline is session budgets, a hard dollar cap you set at session creation. Sessions pause with stop_reason: "budget_reached" when their consumed list cost (public list rates, not your contracted rate) reaches the cap; raise the cap to resume, or set budget: null to remove it (one-way). Amounts are whole US cents as strings ("2500" = $25.00; "25.00" is rejected). Deployments accept the same object and copy it onto each run, so a $20 daily cron budgets $20 per run, not $20 per month. The one gotcha to size around: enforcement is between requests, so a $0.50-capped session can pause at $0.53 (bounded to one request per thread). Same release: advisors as a roster entry ({"type": "advisor", "model": "..."}, one per roster; runs as an invisible anthropic.advisor thread the primary can consult mid-turn; the coordinator's list_agents and send_to_agent can't see it) — the roster form of the same advisor server tool. Also: inference_geo on the model config or as a session override for data residency, and skills auto-discovered from a mounted GitHub repo — any file in the repo's root .claude/skills/ is available to the session at start, no separate registration. What it means: the full session-budget deep-dive — the four-step event sequence at the cap, the "raise by usage.list_cost + 1 cent, never by old max_list_cost" rule, the multiagent shared-cap semantics, and the ops checklist — is at Managed Agents Session Budgets.
  • 🔌 API — Inference Hooks shipped August 5, 2026 in beta for Claude Enterprise — a first-party, HTTPS webhook (not a WebSocket, despite some coverage) that lets your DLP or in-house AI security server allow-or-deny every governed prompt on claude.ai, Claude Code, and Cowork before the model sees it. One config covers all three surfaces. Every request is signed per Standard Webhooks (HMAC-SHA256 over {webhook-id}.{webhook-timestamp}.{raw body} with your whsec_ secret), the verdict is a small JSON object ({"action": "allow"} or {"action": "deny", "deny_reason": "..."} — deliberately no redact today), and the transcript your server sees is what the user sees (text, tool calls, extracted attachment text) — never system prompts, hidden reasoning, or raw file bytes. What it means: the biggest ops levers are the verdict timeout (1–10 000 ms, 5 s default), failure handling (block vs allow uninspected), and the circuit breaker that stops enforcement on sustained failures — get the deep-dive with the two signing bugs that catch every first integration and the shadow → percentage → role-exclusion → enforce rollout playbook at Inference Hooks: inline DLP for Claude Enterprise.
  • 🔌 API (cross-AI) — MCP Apps, the first official Model Context Protocol extension, is now covered in depth on AILmanac. Finalized January 26, 2026 and folded into the 2026-07-28 stateless core spec, MCP Apps lets a server ship an HTML UI that any MCP client renders in a sandboxed iframe, with the iframe speaking JSON-RPC 2.0 over postMessage back to the host. Extension identifier io.modelcontextprotocol/ui, MIME text/html;profile=mcp-app, resources at ui://<server>/<name>, tools link via _meta.ui.resourceUri. Default CSP is connect-src 'none' — a UI cannot fetch anywhere until the resource declares connectDomains. What it means: every UI-initiated write is still a normal tool call the host mediates — Apps can render and propose, they cannot silently execute. The full deep-dive on when it beats a plain result, the wire shapes, and the security model: MCP Apps: Interactive UIs Inside a Tool Call.
  • 🗣️ Apps — Claude Cowork now runs on web + mobile with scheduled tasks — launched July 7, 2026 (Max first, other paid plans rolling in over the following weeks). The architectural shift: Cowork sessions now execute on Anthropic's servers, not your machine, so scheduled tasks run on their cadence with the laptop closed and no device online. Frequency options are hourly / daily / weekdays / weekly / manual (no cron), each run spawns a fresh session with your connectors + skills + plugins, and approval prompts get pushed to your phone mid-run. Local file / browser / computer use stay desktop-only — audit any scheduled prompt for local-machine actions or it'll silently skip them. What it means: the practical playbook (capability-by-surface matrix, the Dispatch-vs-Scheduled-vs-Interactive distinction, and the four gotchas that break silent runs — including OAuth drift and the "if I'm asleep" timeout hole) is at Cowork Scheduled Tasks: Agents That Run With No Device On.
  • 🧠 Models (cross-AI) — OpenAI previewed its "next major model" Astra on August 1, 2026 — not with a keynote, but by pushing ten Lean-4 formalized proofs of previously unsolved problems (sphere packing, Connes rigidity, non-sofic groups, quantum parallel repetition, Ramsey lower bounds, etc.) to openai/ten-proofs. OpenAI described Astra as a multi-agent, long-horizon system that "coordinates multiple agents working together on long-running tasks over hours or days." What it means: there is no API, no pricing, no ChatGPT surface, and no release date — Astra is internal-only and heading into the new U.S. federal review process. The widely-quoted "$2,000" figure is the token cost at Sol's API rates, not Astra's price. Your Claude vs GPT-5.6 vs Gemini decision this month does not change; keep shipping. Full "confirmed vs unknown" breakdown, the ten problems, and a should-I-wait rule of thumb: OpenAI Astra: The Preview Field Note.
  • 🔌 API — Enterprise user-management endpoints entered beta on July 13, 2026 — the Admin API's members and invites endpoints are now callable on Claude Enterprise organizations (in addition to Console), and a new set of RBAC group and custom-role endpoints ships alongside them. Groups and custom-role routes require anthropic-beta: ce-user-management-2026-07-13 and DROP the anthropic-version header; members and invites take neither. Scopes are granular (read:members, write:members, read:rbac_groups, write:rbac_groups, read:org_audit). What it means: you can now automate offboarding, quarterly group audits, and JIT hire onboarding entirely from CI — see the full playbook and the three gotchas at The Admin API: automate your Claude org.
  • 🔌 API — Managed Agents Memory Stores entered public beta on July 22, 2026 — a first-party, server-side persistent-memory primitive for Managed Agents. Stores mount into the session sandbox at /mnt/memory/<slug>/ and the agent reads/writes them with its standard file tools. Every write creates an immutable memory version (30-day retention minimum), you can redact history for compliance, and content_sha256 preconditions give you optimistic concurrency. Limits: 8 stores per session, 2,000 memories per store, 100 kB per memory. What it means: the biggest header gotcha — memory-store endpoints use agent-memory-2026-07-22; session endpoints (including attaching a store) still use managed-agents-2026-04-01, and sending both on the same request returns 400. Full walkthrough: Managed Agents Memory Stores.
  • 🧠 Models — Claude Opus 5 (claude-opus-5) shipped July 24, 2026 — Anthropic's fourth model in two months. Same $5 in / $25 out per MTok pricing as Opus 4.8, same 1M context and 128k output, but materially better numbers: 44.4% on Frontier-Bench v0.1 (vs Opus 4.8's 18.7%), 96.0% on SWE-bench Verified, 30.16% on ARC-AGI-3. Now the default on Claude Max and strongest available on Claude Pro. Two contract changes will break naive migrations: adaptive thinking is on by default and shares your max_tokens budget, and thinking: {"type": "disabled"} now returns 400 at the new xhigh or max effort tiers. What it means: if you pin claude-opus-4-8, read Claude Opus 5: The Field Guide before flipping the ID, and plan the Opus 4.1 → Opus 5 migration before the 5 August 2026 retirement.
  • 🛠️ Claude Code — Screen reader mode shipped July 14, 2026. Turn it on with claude --ax-screen-reader, CLAUDE_AX_SCREEN_READER=1, or "axScreenReader": true in settings: it plain-texts the transcript, hides decorative glyphs, flattens nested tables into Header: value. lines, and announces permission-mode changes aloud when you cycle with Shift+Tab. The same release added vimInsertModeRemaps (map jj → Escape) and mouse-click support in fullscreen menus. What it means: the CLI is now usable with assistive tech and lower-strain input — see Claude Code Accessibility.
  • 🛠️ Claude Code — In-app browser on Desktop (Week 28, July 6–10, 2026): Claude Code on desktop gets a built-in browser, so Claude can pull up docs, designs, or any site and interact with pages the way it already does with local dev-server previews. Also that week: /doctor (alias /checkup) is a full setup checkup that diagnoses and can fix issues, and auto mode now blocks transcript tampering and asks before rm -rf on unresolved variables. What it means: Claude can verify against real web pages without leaving the session, and setup problems get a one-command diagnosis.
  • 🧠 Models — Claude Sonnet 5 shipped June 30, 2026 and is now the default model in Claude Code, with a native 1M-token context window and introductory pricing through August 31, 2026. It's the new balanced "start here" Sonnet tier, superseding Claude Sonnet 4.6 (now a legacy model). What it means: if you pin a model, migrate to claude-sonnet-5 — but read Claude Sonnet 5: The Field Guide first, because non-default temperature/top_p/top_k now returns 400, manual extended thinking returns 400, adaptive thinking is on by default, and the new tokenizer produces ~30% more tokens for the same text. Also check the Current Models & Pricing table for exact IDs and live pricing before relying on a number from a blog post.
  • 🛠️ Claude Code — Dynamic workflows are generally available: ask for one (or set /effort ultracode) and Claude writes a JavaScript script that orchestrates tens to hundreds of subagents in the background — for codebase-wide audits, large migrations, and cross-checked research. Run /deep-research to see the bundled one, or /workflows to watch runs. What it means: you can now take on fleet-scale tasks one conversation could never coordinate, with the orchestration saved as a rerunnable command. See Dynamic Workflows & ultracode.
  • 🧠 Models — A new top-tier model, Claude Fable 5 (claude-fable-5) and its Glasswing-only sibling Mythos 5 (claude-mythos-5) shipped June 9, 2026 on Claude API, Amazon Bedrock, Claude Platform on AWS, Google Cloud and Microsoft Foundry — Anthropic's first "Mythos-class" models, sitting above Opus. They share a 1M-token context, up to 128K output, and $10 / $50 per MTok pricing. What it means: Fable 5 is NOT a drop-in for Opus 4.8 — it refuses in-band as HTTP 200 with stop_reason: "refusal", adaptive thinking is the only mode, raw chain-of-thought is never returned, and Anthropic added a new fallbacks parameter + SDK middleware + fallback-credit billing specifically for retries on Opus 4.8. It also carries mandatory 30-day retention (no ZDR). See the full field guide — Claude Fable 5 & Mythos 5: The Flagship Field Guide.
  • 🛠️ Claude Code — Subagents can now spawn their own subagents (up to 5 levels deep), and /code-review --fix applies review findings to your working tree. What it means: delegation composes deeper, and review can close the loop instead of just reporting. Cross-check the official changelog for exact behavior.
  • 🔌 API — Capabilities like structured output, extended thinking, and prompt caching evolve. What it means: re-check the API section before relying on exact parameters.

Want the firehose?​

This is a digest, not a complete log. For everything:

Next​