Why I picked this
Victor's instinct here cuts to the existential question nobody in AI tooling wants to say out loud: what if the orchestration layer just... evaporates? Swyx surfaces a fascinating tension from inside the model providers themselves — Anthropic's Claude Code team rewrites their harness every 3-4 weeks because they believe the model should do the heavy lifting, not the wrapper. That's not a technical preference, that's a philosophical position. And it puts every company building 'AI agent frameworks' in an awkward spot: you're betting your business on a layer that the people building the actual intelligence think shouldn't exist. The finance analogy is perfect — was it the trader's skill or the institutional seat? Except here, the seat is getting smarter every quarter, and the trader might be obsolete by Q3. This isn't just architecture debate, it's a market structure question with real consequences for where you place your bets.
Three lenses
If I'm building an AI product today, I'm watching this closely but not panicking yet — models still need guardrails, logging, fallback logic, and cost management that someone has to write. The question is whether that 'someone' is a $50M venture-backed framework company or just 200 lines of Python I maintain myself.
The Big Harness vs Big Model debate matters less to me than deployment reality — I need something my team can actually use Monday morning, and right now that's still a framework with docs and support. But if I'm evaluating a vendor whose entire value prop is 'orchestration,' I'm asking hard questions about their moat in 18 months.
Here's what nobody's saying: the framework companies know this is coming, which is why they're all pivoting to 'observability' and 'governance' — the last defensible layer before you're just reselling API credits. Watch for the rebrand wave in Q2.
“I'm not even sure these guys want me to exist - AI framework founder at OpenAI event”
Key takeaways
- Central debate emerging: 'Big Model' (minimal harness, model does everything) vs 'Big Harness' (orchestration/framework layer adds value) - mirrors finance debate about trader skill vs institutional position
- Model providers like Anthropic/OpenAI are philosophically minimalist on harness - Claude Code rewrites from scratch every 3-4 weeks, emphasizing 'thinnest possible wrapper' with all secret sauce in the model itself
- Existential threat to AI framework/orchestration companies as reasoning models improve - framework founders questioning their own necessity as models become more capable of self-orchestration
People mentioned
- Boris Cherny, Engineer @ Anthropic/Claude Code
- Cat Wu, Engineer @ Anthropic/Claude Code
- Ryan Lopopolo, Codex Team @ OpenAI
- Noam Brown, Researcher @ OpenAI
- Swyx, Author/Analyst @ Latent Space
Companies
Key metrics
- •rewritten from scratch every 3-4 weeks
- •$3M in profits (finance analogy)
Why this matters for operators: Critical for operators evaluating build-vs-buy decisions in AI agent infrastructure — reveals philosophical divide between model providers and orchestration vendors that will shape vendor viability over next 12-18 months
I cover AI×GTM intelligence like this every Wednesday.
Get STEEPWORKS WeeklyMore picks
Humans will keep inventing new reasons why we must stay in the loop with agents
- Human resistance to full AI autonomy is not purely technical—it's psychological and organizational; companies will rationalize keeping humans in decision loops even when agents are capable
- The 'human-in-the-loop' requirement may become a self-perpetuating narrative rather than a genuine necessity, driven by organizational risk aversion and change resistance
- Product leaders at scale (Notion) are observing this pattern, suggesting it's a widespread phenomenon across enterprise AI adoption, not isolated to specific use cases
Comp plans for consumption pricing
- Consumption pricing fundamentally breaks traditional SaaS comp models—requires rethinking sales incentive structures around usage vs. contract value
- Four distinct contract structures exist (pay-as-you-go, uncommitted, committed, hybrid), each requiring different compensation mechanics and sales behaviors
- Enterprise consumption-based deals create tension: customers want flexibility, sales teams need predictability for quota attainment—comp design must bridge this gap
3 revenue motions your AI is only half wired into
- Model parity has arrived: OpenAI/Claude now trade evenly on core tasks, making 'better AI' a non-differentiator—the edge shifts to integration depth into existing revenue motions
- Waste is quantified: teams paying $17K-$37K/month for AI seats that never touch pipeline generation; real cost is opportunity cost of unused capacity, not subscription fees
- Lean teams have a structural advantage: cannot out-buy larger competitors on model access, but can out-embed them by wiring AI 1 revenue motion deep (pipeline → content → deals) with proprietary deal context competitors haven't seen
This analysis was produced using the STEEPWORKS system — the same agents, skills, and knowledge architecture available in the GrowthOS package.