"The Folder Is the Agent" https://every.to/source-code/the-folder-is-the-agent-rerun 1 big thing: How this engineer is running 44 AI agents — and the surprisingly simple architecture behind it The industry is spending enormous energy on autonomous swarms. One engineer spent three months there, then found the answer was a folder. Why it matters: Most B2B teams building AI workflows are overcomplicating the architecture and underinvesting in the context. The folder-as-agent model flips that. The sophistication is in the context you build over time — not in the orchestration layer on top. Driving the news: Kieran Klaassen, GM of Every's AI email product Cora, runs 44 specialized AI agents across multiple projects. Each one is just a model pointed at a folder — a project directory with a CLAUDE.md file, skill definitions, institutional knowledge, and accumulated context built through months of use. → A different folder creates a different agent — same model, completely different specialist → A dispatch layer routes work between them; two slash commands replace 20 terminal tabs Zoom in: Anthropic's own research backs the pattern: an Opus lead agent with Sonnet sub-agents outperformed a single Opus agent by 90% on research tasks. → But multi-agent systems burn 15x more tokens than single-agent setups — most coding tasks have fewer parallelizable steps than research Yes, but: You cannot vibe orchestrate. Build the folder, use it yourself, trust it, then hand it off. Skip that step and agents file duplicate issues and open pull requests for work already finished. Be smart: Look at your current AI project folder. Is it a specialist or a generic setup? If your CLAUDE.md is boilerplate from someone's blog post, spend 30 minutes making it yours. That investment compounds every time an agent uses it. The bottom line: The agent is not the model. The agent is the context. Build accordingly. https://every.to/source-code/the-folder-is-the-agent-rerun

Claude Code