I gotta say, the local models are catching up quick. Claude is definitely still ahead, but things are moving right along.
Useful tip.<p>From a strategic standpoint of privacy, cost and control, I immediately went for local models, because that allowed to baseline tradeoffs and it also made it easier to understand where vendor lock-in could happen, or not get too narrow in perspective (e.g. llama.cpp/open router depending on local/cloud [1] ).<p>With the explosion of popularity of CLI tools (claude/continue/codex/kiro/etc) it still makes sense to be able to do the same, even if you can use several strategies to subsidize your cloud costs (being aware of the lack of privacy tradeoffs).<p>I would absolutely pitch that and evals as one small practice that will have compounding value for any "automation" you want to design in the future, because at some point you'll care about cost, risks, accuracy and regressions.<p>[1] - <a href="https://alexhans.github.io/posts/aider-with-open-router.html" rel="nofollow">https://alexhans.github.io/posts/aider-with-open-router.html</a><p>[2] - <a href="https://www.reddit.com/r/LocalLLaMA" rel="nofollow">https://www.reddit.com/r/LocalLLaMA</a>
I think control should be top of the list here. You're talking about building work flows, products and long term practices around something that's inherently non-deterministic.<p>And the probability that any given model you use today is the same as what you use tomorrow is doubly doubtful:<p>1. The model itself will change as they try to improve the cost-per-test improves. This will necessarily make your expectations non-deterministic.<p>2. The "harness" around that model will change as business-cost is tightened and the amount of context around the model is changed to improve the business case which generates the most money.<p>Then there's the "cataclysmic" lockout cost where you accidently use the wrong tool that gets you locked out of the entire ecosystem and you are black listed, like a gambler in vegas who figures out how to count cards and it works until the house's accountant identifies you as a non-negligible customer cost.<p>It's akin to anti-union arguments where everyone "buying" into the cloud AI circus thinks they're going to strike gold and completely ignores the fact that very few will and if they really wanted a better world and more control, they'd unionize and limit their illusions of grandeur. It should be an easy argument to make, but we're seeing about 1/3 of the population are extremely susceptible to greed based illusions.,
can you recommend a setup with ollama and a cli tool? Do you know if I need a licence for Claude if I only use my own local LLM?
I'm confused, wasn't this already available via env vars? ANTHROPIC_BASE_URL and so on, and yes you may have to write a thin proxy to wrap the calls to fit whatever backend you're using.<p>I've been running CC with Qwen3-Coder-30B (FP8) and I find it just as fast, but not nearly as clever.
My experience thus far is that the local models are a) pretty slow and b) prone to making broken tool calls. Because of (a) the iteration loop slows down enough to where I wander off to do other tasks, meaning that (b) is way more problematic because I don't see it for who knows how long.<p>This is, however, a major improvement from ~6 months ago when even a single token `hi` from an agentic CLI could take >3 minutes to generate a response. I suspect the parallel processing of LMStudio 0.4.x and some better tuning of the initial context payload is responsible.<p>6 months from now, who knows?
Openrouter can also be used with claude code. <a href="https://openrouter.ai/docs/guides/claude-code-integration" rel="nofollow">https://openrouter.ai/docs/guides/claude-code-integration</a>
I guess I should be able to use this config to point Claude at the GitHub copilot licensed models (including anthropic models). That’s pretty great. About 2/3 of the way through every day I’m forced to switch from Claude (pro license) to amp free and the different ergonomics are quite jarring. Open source folks get copilot tokens for free so that’s another pro license I don’t have to worry about.
Or they could just let people use their own harnesses again...
They do? That's what the API is.<p>The subscription always seemed clearly advertised for client usage, not general API usage, to me. I don't know why people are surprised after hacking the auth out of the client. (note in clients they can control prompting patterns for caching etc, it can be cheaper)
Or better yet: Connect to some trendy AI (or web3) company's chatbot. It almost always outputs good coding tips
i mean the other obvious answer is to plug in to the other claude code proxies that other model companies have made for you:<p><a href="https://docs.z.ai/devpack/tool/claude" rel="nofollow">https://docs.z.ai/devpack/tool/claude</a><p><a href="https://www.cerebras.ai/blog/introducing-cerebras-code" rel="nofollow">https://www.cerebras.ai/blog/introducing-cerebras-code</a><p>or i guess one of the hosted gpu providers<p>if you're basically a homelabber and wanted an excuse to run quantized models on your own device go for it but dont lie and mutter under your own tin foil hat that its a realistic replacement
Or just don’t use Claude Code and use Codex CLI. I have yet to hit a quota with Codex working all day. I hit the Claude limits within an hour or less.<p>This is with my regular $20/month ChatGpT subscription and my $200 a year (company reimbursed) Claude subscription.