
What happened
A developer rebuilt Claude Code's agent architecture in CrewAI, an open-source framework, and found that the gap between a basic agent loop and Claude Code's capability comes from the surrounding machinery—planning, memory, sandboxing, subagent delegation, and approval systems—not the underlying language model itself.
Why it matters
Most teams underestimate how much engineering sits outside the model. A bare agent loop fails on real codebases (reads wrong files, loses context, fills memory with stale output), while Claude Code stays on track. Understanding this split—model as "brain" deciding actions, harness as "hands" executing them—shows what you actually need to build reliable coding agents in production.
What to watch
The rebuild tested against a small BankAccount class with two real bugs and five tests. The harness took the project from 3 failing and 2 passing to all 5 passing, demonstrating that planning, subagents, and sandboxing together enable the agent to fix code correctly without shortcuts like editing tests.
Ask the AI about this article →
Summaries like this, in your inbox every morning.
The article traces a common misconception: that Claude Code's power lies in Anthropic's language model. The actual insight is architectural. A basic agent loop—send task, run tools, repeat—can be written in thirty lines, yet it crumbles on real codebases because it lacks the surrounding machinery. Context rot, the slow degradation where the original goal gets crowded out by intermediate results, is a structural problem that no amount of model capability alone solves. This is where the harness layers in: planning builds a high-level roadmap; subagents delegate work to specialist contexts so the main agent doesn't hold gigabytes of file reads in memory; memory persists facts across sessions so the agent doesn't start from zero each time; and sandboxing plus approval loops provide safety without relying on prompts. The article demonstrates this by rebuilding Claude Code's architecture in CrewAI, an open-source framework. Most layers map onto built-in features—the loop, tools, planning, delegation, and memory are framework responsibilities—but three critical pieces remain the engineer's job: prompt design (role, goal, backstory of each agent), sandbox setup, and tool assignment. The test case (fixing a BankAccount class with two real bugs) confirms the hypothesis: the complete harness outperforms a bare loop not because the model is smarter, but because the harness keeps it focused, manages its memory, distributes work, and enforces safety. Cost is a trade-off: planning, subagents, and looping add API calls, so complex agent setups can become expensive.
For example, today's edition would include:
AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. Q&As are published on this page for other readers too.
Fukushima Prefecture ran a proof-of-concept in fiscal 2025 with 100 paid accounts for two generative AI servic…

Azoma, an Agentic Commerce Optimisation platform, published what brands and digital shelf teams should look fo…

OpenAI, WAN-IFRA, and AIRPPU announced a joint initiative to help Ukrainian news organizations adopt AI

DeepSeek is reportedly planning to buy 160,000 Huawei chips for its 1 GW data center under construction in Inn…

OpenAI has stated it is 'now moving into the AGI era,' and the company has also said it believes it knows how…

Artificial Analysis updated its Intelligence Index to v4.2 on September 4, adding two new tests: AA-Briefcase…
