12 reads.
A tight framing of the shift everyone's circling: you stop prompting the agent and start building the system that prompts it. Schedule, discover, build, verify, repeat. Worth it as the one-line mental model before you read anything longer on loops.
The announcement: Claude now joins Slack as a taggable team member for Enterprise and Team plans. Worth noting because Slack, not a terminal, is where most teams already coordinate, and putting the agent there changes who ends up using it. The reference point for the human-agent-teams conversation that followed.
Andreessen's long, unusually good essay reframing SpaceX as the one company assembling the full stack for a post-scarcity future: cheap launch, orbital compute, lunar industry, Mars. The engineering-culture sections carry it, especially Musk's five-step Algorithm and the idiot index. Not AI-specific, but the orbital-data-center thesis ties directly to where compute and energy are heading. A real sit-down read.
The best long read on why a top-tier model isn't the point. The system around it is. Loops, memory, verifier sub-agents, and state files are what make each run leave the next one smarter, and the piece lays out the whole stack with cost-routing advice for when to reach for the expensive model versus a cheap one. Long, but it's the map most people are missing.
An Anthropic engineer on two things the top model changes: self-correction loops and memory. The sharpest takeaway is that the model shouldn't grade its own work. An independent verifier explores harder and recovers from dead ends where self-critique stalls at good enough. Short, concrete, and from someone who actually ran the experiments.
The best explainer on the phrase everyone was repeating without defining. A loop is cron plus a decision-maker in the body: the model, not a hardcoded script, picks the next move each tick. The punchlines land, that the loop, not the model, is now the expensive part, and that the real asset is the skills a loop calls, not the loop itself. If you read one thing on loops, this.
A plain-English tour of the Claude features hiding in plain sight: Projects, memory, extended thinking, scheduled tasks, prompt caching, custom roles. Nothing exotic, but the value is in the framing. Each one takes minutes to set up and pays off daily. Good to forward to anyone still treating Claude as a fancier search box.
Anthropic's own writeup on building agents that do data analysis. The useful parts are the unglamorous ones: skills, clean data foundations, and evaluations. If you're wiring an agent into real business numbers, this is the part everyone skips and then regrets.
The line most people skim: every agent in a workflow can run a different model. This is the proof. A 33-agent audit, cheap readers plus one smart synthesizer, ran in under five minutes and found a real buried error. Put the expensive model where the thinking happens and run the rest on the cheap one. That's the economics of parallel agents in one example.
A short thread on a real problem: when agents do the work, how do you actually understand what got done? The value is in seeing how people inside Anthropic keep oversight without babysitting. Worth a scroll if your agents are starting to outrun your attention.
The canonical piece on dynamic workflows, from the Anthropic engineer who built them. Claude writes its own custom harness on the fly to beat the failure modes of one long context window: laziness, self-preference, goal drift. The example prompts alone are worth the read, and it names the reusable patterns (fan-out, adversarial verify, tournament) you'll see everywhere else. Start here.
The reference for anyone configuring Claude Code seriously. It walks the whole control center: CLAUDE.md, path-scoped rules, and hooks, with the key nuance that instructions are suggestions but hooks are deterministic. Keep CLAUDE.md under 200 lines or adherence drops. This is the one to bookmark.