DeepClaude: I Combined Claude Code with DeepSeek V4 Pro in My Agent Loop and the Numbers Threw Me Off

DeepSeek V4 Pro correctly solves 94% of deep reasoning tasks in my loop… but the latency cost makes it unusable for 60% of my agent cases. Yeah, you read that right. And that completely blows up the narrative of "combining models is always better."

Tuesday night I watched the DeepClaude post climb to 467 points on Hacker News. What caught me wasn't the repo itself — it was a comment buried on page 2: "The dual architecture makes theoretical sense, but nobody measured whether the orchestration overhead destroys the benefit in real loops." Three hours later I had the experiment running.

I've written before about how I use YAML specs for my agents and about how Kimi K2.6's benchmarks surprised me against my real cases .…