Claude AI Updates

Anthropic recently acquired Fercept, an AI perception startup that teaches Claude to see and interact with software just like you do. This means Claude is learning to literally navigate spreadsheets, fill out web forms, and click buttons. The acquisition matters because it expands what Claude can do beyond answering questions or writing code into actually using your computer.

Internally, Anthropic built a system called CASH (Claude accelerates sustainable hypergrowth). It’s an internal system where Claude runs the entire growth loop itself: identifying opportunities, building features, testing quality, and analyzing results. As one executive put it, Claude is growing itself. This matters because it shows AI can accelerate its own development, not just assist human developers.

Claude Opus 4.6 introduced Adaptive Thinking, which lets Claude automatically decide how deeply to reason for each task. It uses effort levels from low for quick answers to max for peak intelligence, optimizing cost and performance without you toggling settings. This matters because it removes guesswork from using AI efficiently.

On the infrastructure side, over a thousand companies now spend more than a million a year on Claude, with that number doubling in under two months. Anthropic trains Claude across Google TPUs, AWS Trainium, and Nvidia GPUs — three hardware stacks for one model, creating zero single points of failure. This matters because it shows how scalability and reliability are built into the platform to match growing demand.

Claude AI updates bring powerful new ways to catch bugs (errors in your code) and improve your work. The /ultrareview command is a key update that catches bugs Claude missed on its own. To use it, you need Claude Code version 2.1.86 or later and must be signed in with a Claude account — an API key (access code for developers) alone won't work. When you run /ultrareview, it can take 10 to 20 minutes, but it runs in the background so you can keep working. For faster feedback on everything, use /review instead.

Every new conversation costs you time and tokens (units that measure AI processing). To avoid starting from scratch, use Claude.md files and memory files. These are plain text files you write to give Claude persistent project instructions. If you miss an update on one of these files, Claude can still work from your corrections.

Another update lets Claude automatically record and recall memories as it works, with no manual prompting required. Version 2.1.32 introduced agent teams, which is a research preview for multi-agent collaboration. With a bug fix update like 2.1.32, you get three new features, four improvements, and five bug fixes.

When Claude detects you correcting it repeatedly for the same mistake, it can autogenerate a rule from those corrections. Your frustrations become permanent guardrails (safety limits) so Claude learns from failures and develops new updates fresh without extra baggage. Start with /review for quick checks, then use /ultrareview for deep bug catching.

Claude Code has several pitfalls and bugs that beginners should watch for. A common mistake is starting new conversations repeatedly, which costs time and tokens getting Claude up to speed. To avoid this, use Claude.md files (plain text files with persistent project instructions) and memory files that Claude reads automatically.

For catching bugs Claude missed, use the `/ultra review` command in Claude Code version 2.1.86 or later. You must sign in with a Claude account (an API key alone won't work). The review runs in the background for 10 to 20 minutes, so you can keep working. Use `/review` for faster feedback on everything else.

New plugins help prevent repeated mistakes. Hookify detects when you correct Claude for the same error and autogenerates rules from those corrections — your frustrations become permanent guardrails. Without it, Claude repeats the exact mistakes you already fixed.

Another best practice: use the "superpowers" skill, which forces Claude to plan before writing code, working in an isolated environment so nothing breaks your main project. It writes tests first, mimicking a senior developer.

Don't use default prompts — that produces generic "AI slop." Plan inside regular Claude, then bring the refined plan into Claude Design for better results.

Two security findings stand out. First, Claude is dramatically better at finding vulnerabilities than exploiting them — defenders currently have the advantage. Second, Claude Code's code revealed unannounced feature flags like "proactive mode," where Claude would work around the clock on tasks. Bug-wise, Claude is learning from failures and developing updates without extra baggage, so update regularly.