Anthropic

Anthropic’s Claude Code Voice Mode went live today in a staged rollout. If you’re on a Pro, Max, Team, or Enterprise plan, here’s everything you need to get started — or get ready when it hits your account. Prerequisites Before you try to enable Voice Mode, confirm you have: Claude Code CLI installed — latest version recommended Eligible plan: Pro, Max, Team, or Enterprise (free plans are not included in this rollout) Active Claude Code session in a terminal environment with microphone access Rollout access: Currently ~5% of eligible users. If the command doesn’t work yet, you’re in the queue — broader rollout is coming in the next few weeks Check your Claude Code version: ...

Anthropic has quietly flipped one of the most-requested switches in AI-assisted development: you can now talk to Claude Code. As of today, Voice Mode is rolling out to Claude Code users — starting with roughly 5% of subscribers — letting developers speak their commands instead of type them. It’s a small percentage to start, but the implications are significant. Hands-free coding has gone from a demo concept to a live feature in one of the most-used AI coding tools in the world. ...

Anthropic’s Claude went down twice in under 24 hours this week — and the developer community’s reaction tells a story about something bigger than a couple of bad server days. The second outage hit on March 3, investigation commencing at 03:15 UTC. It followed Monday’s first disruption, which Anthropic attributed to unprecedented demand. Chat, API, and Claude Code were all affected. Developers watched their pipelines stall, their autonomous agents go quiet, and their Claude Code sessions freeze mid-task — again. ...

Two significant moves from Anthropic landed today, and they’re clearly designed to work together: Claude memory is now available on the free tier, and a new import tool lets users bring their ChatGPT and Gemini conversation history into Claude. Both features went live March 2, 2026 — confirmed across Engadget, 9to5Mac, MacRumors, AndroidHeadlines, and Bloomberg. If you’ve been evaluating Claude as a reasoning backbone for agentic workflows, this changes the accessibility calculus significantly. ...

If OpenClaw is throwing 403 permission_error when it tries to call Claude, your OAuth session has been revoked by Anthropic. This is not a bug you can wait out — it’s a deliberate policy change. Here’s exactly what to do. Time estimate: 10–20 minutes Difficulty: Easy Who this affects: OpenClaw users who signed in with Claude Pro or Max subscription credentials (OAuth flow) rather than a direct API key First: Confirm You’re Affected Check your OpenClaw logs. If you see something like: ...

If you’ve been using OpenClaw with a Claude Pro or Max subscription via OAuth and suddenly started seeing 403 permission_error responses, you’re not alone — and the cause is not a bug you can wait out. Anthropic is actively and deliberately revoking OAuth token access for Claude Pro and Max subscriptions in third-party applications. OpenClaw is among the affected platforms. This isn’t just a version regression or a temporary outage. Multiple independent sources — a Medium post documenting a full migration away from Claude, an analysis on daveswift.com, and a GitHub commit trail — all confirm this is a deliberate policy shift. ...

Claude went dark on Monday morning, and for once it wasn’t a minor hiccup. Starting around 11:49 UTC on March 2, 2026, Anthropic’s consumer-facing AI products — Claude.ai, Claude Code, and the mobile app — began reporting widespread failures. Users across North America, Europe, and Asia flooded social media with screenshots of error pages, spinning loaders, and authentication failures. Anthropic’s official response came quickly: the company cited “unprecedented demand over the past week” as the root cause of service degradation. The statement, confirmed by Bloomberg and CNET, framed this as a capacity problem rather than a security incident — but it raised more questions than it answered. ...

If you run Claude Code in production, v2.1.63 is not a routine patch. This release ships a meaningful architectural shift — HTTP hooks — alongside two genuinely useful slash commands and a pile of memory leak fixes that explain why long-running Claude Code sessions sometimes go sideways. The Big One: HTTP Hooks Replace Shell-Based Hooks Previous versions of Claude Code let you hook into the agent lifecycle via shell commands. It worked, but it was clunky: you were spawning subprocesses, dealing with shell escaping, and losing type safety the moment data crossed the boundary. ...

On March 1, 2026, Claude climbed to the #1 position on the US App Store Top Free chart, surpassing ChatGPT. The milestone has been confirmed across five major outlets — Axios, CNBC, Business Insider, Digital Trends, and TechFusionist — and the timing tells you everything you need to know about why it happened. The Pentagon Flashpoint The catalyst is OpenAI’s agreement to supply AI capabilities to the US Department of Defense — specifically, the deployment of AI for military targeting and weapons systems analysis. When the terms of that arrangement became public, a significant segment of users who had chosen AI tools partly on the basis of developer ethics found themselves reconsidering. ...

Claude Code v2.1.63 ships a significant change to how you hook into the agent lifecycle: shell-based hooks are out, HTTP webhooks are in. If you’ve been using hooks in your Claude Code pipeline, this guide walks through the migration and shows you why the new pattern is worth the effort. Why HTTP Hooks? The old shell hook model had a fundamental problem: crossing the shell boundary destroyed structure. You serialized data to a string, passed it through a shell command, and parsed it back out on the other side. Every step introduced escaping issues, subprocess overhead, and opportunities for silent failure. ...