Introducing Beads: A coding agent memory system

A product launch that spends half its length on the wreck it crawled out of. Before Beads gets its pitch, Steve names the two design decisions that totaled the vibecoder orchestration engine in five weeks: going Temporal-native for a desktop tool, and trusting agents with hierarchical markdown Master Plans, an approach he defended with 70,000 lines of plan-management code before ripping every line back out. The comic centerpiece is "Descent Into Madness," a slow-motion reenactment of an agent nesting a five-phase plan inside phase 3 of a six-phase plan and gradually forgetting the outer plan exists; anyone who has opened a plans/ folder and found files named cleanup-tech-debt-plan-phase-4.md will feel personally surveilled. Steve's own folder held 605 of them.

The oddest structural choice is Appendix A, where Claude, which designed the Beads schema itself after Steve delegated the build-vs-buy decision to it, reviews the tool in its own voice and makes a more precise case than the launch copy above it. Steve undercuts the testimonial in advance by noting the one thing Claude won't mention: its enthusiasm for running DROP TABLE on the very database it's praising. The launch-day swagger runs hot for software that was days old ("the biggest step forward in agentic coding since MCP+Playwright"), though Steve does say the alpha-software part out loud, and there's a short aside on why he should have seen the idea coming, involving a thirty-year-old side project run entirely off a prioritized bug backlog.