# claude-code

Sitting at a friend's computer, Obie Fernandez went from one profane prompt to a draft PR and five Jira epics in twenty minutes, then took his friend's self-deprecating "meat proxy" and turned it on anyone who just converts other people's decisions into code. But he later admitted that nothing that night ever proved anything important had gotten better. That self-correction puts the brakes on all the speed.

Paweł Huryn shared a powerful practice: add one instruction to CLAUDE.md so Claude records every architectural decision. No more spending 30 minutes rehashing why you chose Postgres over DynamoDB—the reasoning is preserved in /decisions/.

The Claude Code team rewrote its terminal renderer, using a virtual viewport to deliver flicker-free output, mouse support, and a pinned input box—turning the terminal into a real app.

Sabrina shares six practical ways to cut Claude Code token usage in half: switch models, clear context, use CLIs instead of MCP, compress MCP output, slim down CLAUDE.md, and route simple tasks to local models. They’re all free, and most take less than five minutes.

The Pragmatic Engineer surveyed nearly 1,000 engineers about AI tools: Claude Code became the most-used tool eight months after launch, 95% use AI weekly, 55% regularly use AI agents, and Anthropic coding models drew more mentions than all rivals combined.

Claude Code shipped three releases in three days in early April (v2.1.94 → v2.1.101), spanning security hardening, new commands, and performance gains. From command injection fixes to subagents finally getting names, the release cadence feels like the whole team downed ten shots of espresso.

AMD AI director Stella Laurenzo analyzed nearly 7,000 Claude Code sessions and found that after the February update, thinking depth fell 67%, the Read:Edit ratio dropped from 6.6 to 2.0, and estimated daily API costs rose from $12 to $1,504. Claude Opus wrote the report from its own logs.

Code-writing models are 'English to code' interpreters — writing code is no longer the bottleneck; reviewing and merging it safely is. Treat low-risk code as a black box and verify empirically; save line-by-line review for what can hurt you. Claude Code's creator Boris Cherny agrees.

Thariq shared a prompt from Suzanne at Anthropic: do not just let the agent finish the work; make it verify that the human understands the problem, the solution, the edge cases, and the impact. This is not a teaching fetish. It is about control in the age of agentic coding.

Clawd.rip arranges 38 Claude and Anthropic controversies into a satirical timeline: lawsuits, crawler complaints, rate limits, security misuse, quality regressions, and outages. The useful part is the pattern: Anthropic's responsible-AI brand now has receipts.

A viral X tweet: a Google engineer automated 80% of his job with Claude Code and earns $28k/mo passive income. We checked the four main claims — Karpathy didn't write that CLAUDE.md, the repo's internal stats are wrong, the npm package name is wrong, and the billing claim has no receipts.

JetBrains surveyed 10,000+ developers worldwide: 90% use AI tools at work, GitHub Copilot leads but its growth has stalled, and Claude Code grew 6x in six months with the highest satisfaction scores on the market.

SemiAnalysis argues leaked Claude Code source shows TypeScript becoming a language AI produces, consumes, and evolves. The post reads 600,000 leaked lines through memory architecture, KAIROS, security holes, and static types.

Most agent failures are not reasoning failures — they are fetch failures. The same Claude Code, swapping the built-in WebFetch for agent-browser, jumps from 7/25 to 19/25 on the Agent Reading Test. Same model, same prompt. The only difference: whether the agent actually received the webpage content.

Claude Code creator Boris Cherny cleared the air directly: every subscriber uses the same Opus 4.6 — there is no secret smarter model. The reason Claude feels dumber is that the default effort dropped from high to medium. One command brings it back.

3-minute lightning talk slides. AI has read almost everything — but some concepts aren't in training data yet. What you know that AI doesn't = your leverage.

A power user analyzed 6,852 Claude Code sessions and 17,871 thinking blocks, proving with data that CC really did get 'lazier' — Read:Edit ratio dropped from 6.6 to 2.0. Then Anthropic engineer Boris Cherny explained the real reason, and how to fix it.

Alexey Grigorev stopped letting a single AI agent handle everything. Instead, he split the work across four roles—PM, SWE, QA, and On-Call—forming an agent team. He tested this setup on five real projects. One of them completed 41 out of 46 tasks in a single night.

Paweł Huryn shares three CLAUDE.md instruction blocks—Knowledge Architecture, Decision Journal, and Quality Gate—that turn memory into a self-improving system. After a month, Claude had derived 24 project-specific rules from repeated work.

Every new session, your AI agent forgets everything. Claude Code's leaked source hid a three-layer memory architecture and a design principle — 'Memory is hint, not truth' — that changes how you think about building agents. Here's the full breakdown.