BLOG

Engineering insights, technical deep-dives, and perspectives on building software.

More Articles

THE AGENT TEAM PROBLEM: SEVEN OPEN-SOURCE APPROACHES TO ORCHESTRATING AI CODING AGENTS

One agent is useful. Multiple agents working in parallel on the same codebase is an unsolved engineering problem. We performed a source-level analysis of seven open-source projects — OrbitDock, codex-autorunner, Squad, Open-Inspect, Multica, Symphony, and AionUi — to map the architectural design space of AI agent orchestration. What emerged are four fundamental disagreements about how humans and AI should collaborate on code.

THE HARNESS THAT MAKES THE MODEL USEFUL: A SOURCE-LEVEL STUDY OF CLAUDE CODE

A 513,237-line TypeScript codebase. 1,902 source files. 40 tools, 101 commands, 20 service modules, 8 task execution types. We performed a complete source-level analysis of Claude Code to answer one question: what does it actually take to turn a language model into a reliable coding agent? This is not a product review — it is a technical reference grounded entirely in source code.

INSIDE CLAUDE CODE: HOW A 513K-LINE CODEBASE TURNS AN LLM INTO A CODING AGENT

We analyzed Claude Code's 1,900+ file codebase — 512K lines, 90% written by Claude itself, 85K+ GitHub stars. What we found is not just an AI wrapper — it's a terminal-native IDE with its own rendering engine, multi-agent orchestration, and a multi-layered permission system.

WHAT KIND OF CONTEXT SEARCH ENGINE DO WE ACTUALLY NEED?

AI coding assistants burn thousands of tokens just figuring out where they are. The context retrieval problem is the real bottleneck — and the solutions look nothing like traditional search.