# agentic-coding

Anthropic engineer trq212 shares his methodology for coding with Claude Fable 5: the bottleneck isn't model capability anymore—it's whether users can surface their 'unknowns' before, during, and after implementation. Includes prompt examples plus HTML artifacts for visualizing blind spots and plans.

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.

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.

gu-log had 336 AI-translated posts. We thought they were 'fine' — until we built a multi-agent scoring system and discovered 74% needed rewriting. This is the story of how we designed the eval, ran it overnight, and what we learned.

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.

Simon Willison's Agentic Engineering Patterns, Chapter 3: AI should help us ship better code, not worse. Technical debt cleanup costs near zero now, architecture decisions can be validated with prototypes instead of guesses, and quality compounds over time.

Simon Willison's First Run the Tests pattern is four words with three effects: the agent learns the test command, gauges codebase size, and shifts into a test-maintenance mindset. Tiny instruction, large behavioral nudge.

Simon Willison shared his agentic engineering playbook at the Pragmatic Summit — five tokens to start TDD, Showboat for manual verification, reverse-engineering six frameworks into a standard, and why bad code is a choice you make.

OpenClaw's ACP lets you spawn Codex, Claude Code, and Gemini from Discord/Telegram chat. Now with Telegram topic binding, persistent bindings that survive restarts, ACP Provenance for audit trails, and more. (Updated 2026-03-09)

Simon Willison's new Agentic Engineering anti-pattern hits hard: do not submit AI-generated code you have not personally verified. That is not saving time; it is stealing reviewer time. The post pairs principles with a terraform destroy horror story.

Cursor launches always-on background agents (Automations) — self-healing CI, auto-approving PRs, security review, and team memory. This marks the paradigm shift from Coding Assistant to Self-Driving Codebase.

Simon Willison introduces Agentic Manual Testing: let AI agents manually operate code and UI like humans do, catching bugs that automated tests miss. With Playwright, Rodney, and Showboat, the 'tests pass but it's broken' nightmare becomes a thing of the past.

The core message: most people do not fail because the model is weak; they fail because context management is messy. Start with a minimal CLI workflow, then iterate through rules, skills, and clear endpoints until agent behavior converges.

Chapter 5 of Simon Willison's Agentic Engineering Patterns: Interactive Explanations. Core thesis: instead of staring at AI-generated code trying to understand it, ask your agent to build an interactive animation that shows you how the algorithm works. Pay down cognitive debt visually.

Anthropic killed third-party OAuth tokens, leaving the official Claude CLI as the way to use a subscription programmatically. This guide covers claude -p input methods, output formats, JSON schema, tool whitelisting, sessions, streaming, and wrappers.

A two-person boutique law firm uses Claude to handle the workload of over a dozen associates, from contract review to legal research. Ten years of practice knowledge became Claude Skills, and general-purpose AI outperformed legal vertical tools.

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.

Cursor CEO drops three data points marking a tectonic shift: agent usage grew 15x, Tab-to-Agent ratio flipped to 1:2, and 35% of Cursor's PRs come from autonomous cloud agents. We're not coding anymore — we're building the factory (╯°□°)╯

Chapter 4 of Simon Willison's Agentic Engineering Patterns: Hoard Things You Know How to Do. Core thesis: every problem you've solved should leave behind working code, because coding agents can recombine your old solutions into things you never imagined.

Karpathy says coding agents started working in December 2025 as a hard discontinuity. He built a DGX Spark video analysis dashboard in 30 minutes from one English sentence. Programming is becoming agent direction, not typing.