Cheaper tokens in the $200 subscription.

Correct me if I'm wrong, but using Pi etc you're paying the full API price.

Well, I'd love to use an open-source harness! My issue is that Opus 5.5 / Fable 5.1 has been the best model for me to work with, and it's way cheaper to use it with the subscription to Claude Code Max. I won't pay more just to use an open-source harness. I'd rather just wait it out and stay on Claude Code not having to constantly jump around / switch tools as the industry matures.

1. A lot of people already have Claude Code set up, and it's easier to keep using that than to install something new.

2. Lots of people are used to Claude Code's interface/commands/etc. and don't feel like paying the cost of learning something new. The benefits would have to outweigh those switching costs, and it's unclear that they do.

3. Claude Code already works with your Claude MAX subscription[0], which gives you an incredible amount of usage of the top-tier models for cheap, which can't be matched by any open-source options. And most people won't exhaust this usage, so they have no real need to use open-source models.

4. Although it's hard to 100% confirm this, there's reason to believe that Claude itself works better with Claude Code than with other harnesses.

5. There's no real lock-in. If tomorrow you decide you don't want to use Claude Code, you can just switch to something else ezpz. So there's no reason to worry that you're digging a hole and locking yourself in. Thus, there's no urgency to switch away.

[0] Yes, open-source harnesses can use your Claude MAX subscription, but does this "benefit" of open-source harnesses really outweigh the costs of #1, #2, and #4 above?

There's just not really any features in an open-source harness that blow my mind enough to move off the highly-subsidized claude code subscription. I type in instructions and it spits out code. I'm increasingly of the opinion that the more complex features being floated are productivity theater.

Why would you not just build your own harness in October 2026? Gateway, memory, tool calls, LLM api - the basics are pretty simple to get started and get to a point where your harness can be self-improving to add any new features that you need.

better discounts when compare with API cost, and frontier lab harnesses and models are tuned to each other

Claude Code wont let me use their sub with one as far as I remember. So I'm stuck with their convoluted TUI. It does what I need, and when it doesn't I just build tools that Claude consumes. The new "Artifacts" feature has helped a bit though.

A main criteria in 2026 should be whether the harness gives you access to all model families for just the harness author's models.

More and more harnesses are headed this way, there are two notable holdouts.

If you tell me I should OpenCode over Claude Code in October 2026 - then you have no idea what you are talking about.