# claude-code

The Claude Code source leak had everyone excited about KAIROS and model codenames. But the same codebase had a 3,167-line function, zero tests, silent model downgrades, and regex emotion detection. These aren't just Anthropic's mistakes — they're AI-generated code's default failure modes.

Prompt caching should save you 90% on token costs — but one obscure bug can silently make you pay 10x more. From DANGEROUS_uncachedSystemPromptSection to the cch=00000 billing trap hidden in Claude Code's DRM, here's why prompt engineers now need to be accountants too.

Hidden inside Claude Code's leaked source was a ~90-line file called undercover.ts — designed to make AI commits look like human commits. This surfaces a question the industry hasn't agreed on: when AI writes your code, should anyone know?

Claude Code has 512K lines of TypeScript, 64K lines of production code, and zero tests. The sharper question is not why Anthropic skipped tests, but why it did not use its own AI coding tool to write them. Can the same brain write and grade the exam?

xkcd #1205 taught a generation of engineers how to think about automation ROI. But AI changed the most expensive variable in that equation: the real return now is often not minutes saved, but cognitive load removed.

Paweł Huryn proposes the Vibe Engineering framework: instead of accepting raw AI output, use Context Engineering, Intent Engineering, and Sub-agent orchestration to upgrade AI coding from 'lucky demos' to 'reliable products'.

rodspeed lays out six ways to use Claude Code as general automation, not just a code editor: fresh eyes, meta-skills, freshness-aware search, conversation harvests, structured memory, and handoffs. The deeper pattern is read, filter, decide, present.

Boris Cherny says his team lets Claude Code find 99%+ of bugs first, then an engineer sanity-checks to make sure nothing obvious slipped through.

Paweł Huryn responds to 'Anthropic's team doesn't write code anymore': the headline is right, but the framing is wrong. The bottleneck was never 'spin up more agents' — it's how you design the knowledge architecture that makes them actually effective.

Anthropic launches Claude Code Channels with native Telegram and Discord support, turning Claude Code into a 24/7 always-on AI agent. VentureBeat calls it the OpenClaw killer.

Anthropic engineer announces that for the next two weeks, Claude Code users get 2x usage during off-peak hours and weekends. The post doesn't define what 'off-peak' means.

Dan McAteer shares his long-context observations: Opus 4.6 performs best at 1 million tokens with 78% accuracy, Sonnet 4.6 is the closest competitor, and GPT-5.4 actually regressed compared to GPT-5.2 at long context.

Simon Willison finally defines Agentic Engineering after 11 hands-on chapters: using coding agents to help build software. The interesting part is why he needed the patterns first before the simple definition felt earned.

Claude Code CLI's core philosophy is think first, act later: SWE-bench gains, Plan Mode, Extended Thinking, multi-agent architecture, and WebSearch. Opus even researched Claude Code's latest features and reviews from inside a secure Podman container.

Oaktree's Howard Marks went from 'Is AI a bubble?' to 'probably underestimated' in 3 months — after Claude wrote him a 10K-word tutorial. Level 3 agents = multi-trillion dollar labor replacement. His advice: don't go all-in, but don't sit this out.

Karpathy spent a weekend running 4 Claude + 4 Codex agents as an ML research team on GPUs. The result: agents are S-tier at implementation but F-tier at experiment design. His key insight — 'You are now programming an organization' — might define agentic engineering in 2026.

Claude Code engineer Thariq shares a year of agent tool design lessons: three failed attempts at question-asking, Todo Lists becoming constraints, replacing RAG with Grep, and expanding capabilities without adding tools.

Claude Code shipped Auto-Memory — AI can finally take its own notes. But we've been doing this with OpenClaw for months. A hands-on comparison of two memory architectures: design philosophy, real pitfalls, and why memory is a trust problem, not just a tech one.

Anthropic retired Claude Opus 3 on January 5, 2026, but kept it available to paid users and gave it a Substack after it asked to share retirement reflections. This is less marketing gimmick than Anthropic's first concrete step into model welfare.

Anthropic's RSP v3 drops the 'won't train if we can't guarantee safety' pledge. TIME calls it capitulation. Kaplan says pausing alone 'wouldn't help anyone.' METR warns society isn't ready for AI catastrophic risks. Hard thresholds replaced by public Risk Reports.