Pete Winn 🔆

The thing you are supposed to be decentralizing is power.

Sequoia's thesis that the next $1T company will sell work, not software, is the most important reframe in AI right now. The argument: if you sell a copilot, you're competing with every new model release. But if you sell the outcome — books closed, contracts reviewed, claims handled — every AI improvement makes your margins better, not your product obsolete. The key insight most people miss: for every $1 spent on software, ~$6 is spent on services. The entire SaaS playbook was about capturing the software dollar. The AI playbook is about capturing the services dollar — at software margins. Not "AI for accountants." The AI accounting firm. Not "AI for lawyers." The AI law firm. The companies that figure this out won't look like SaaS companies. They'll look like services firms rebuilt on software infrastructure. That's a fundamentally different company to build, fund, and scale. And most founders are still building copilots.

Based on everything explored in the source code, here's the full technical recipe behind Claude Code's memory architecture: [shared by claude code] Claude Code’s memory system is actually insanely well-designed. It isn't like “store everything” but constrained, structured and self-healing memory. The architecture is doing a few very non-obvious things: > Memory = index, not storage + MEMORY.md is always loaded, but it’s just pointers (~150 chars/line) + actual knowledge lives outside, fetched only when needed > 3-layer design (bandwidth aware) + index (always) + topic files (on-demand) + transcripts (never read, only grep’d) > Strict write discipline + write to file → then update index + never dump content into the index + prevents entropy / context pollution > Background “memory rewriting” (autoDream) + merges, dedupes, removes contradictions + converts vague → absolute + aggressively prunes + memory is continuously edited, not appended > Staleness is first-class + if memory ≠ reality → memory is wrong + code-derived facts are never stored + index is forcibly truncated > Isolation matters + consolidation runs in a forked subagent + limited tools → prevents corruption of main context > Retrieval is skeptical, not blind + memory is a hint, not truth + model must verify before using > What they don’t store is the real insight + no debugging logs, no code structure, no PR history + if it’s derivable, don’t persist it

never buy a 16GB RAM laptop in 2026. you’ll regret it within a week

There's such a deep misunderstanding out there about tmux and I get so many absurd issue reports demonstrating that. Many don't realize that using them is like running a Windows VM on your Mac, and complaining to Apple that iCloud sync isn't working from Windows in the VM. They are super powerful and have their use and I am happy to support them in any way I can. I'm not anti-multiplexer, but I wish more people understood the architecture a bit more.