I wrote a script to run Claude Code with my local LLM, and skipping the cloud has never been easier
… Privacy aside, I also just like running things locally when I can. …
… Privacy aside, I also just like running things locally when I can. …
… For a privacy-conscious user, this is a crucial middle ground. …
… It may also be a concern for privacy-conscious users. While Claude can view your screen to interpret context, it processes images locally first and applies privacy safeguards before sending data to the cloud. …
… They can read your repository, make changes across multiple files, run commands, and iterate on tasks. …
… The choice comes down to two different scenarios: speed and workflow maturity vs. privacy and cost. With Claude, you get faster iterations, lower cognitive load, and less setup friction, whereas local LLMs give you more control and privacy at the cost of more configuration and deliberate setup. …
… The privacy concern isn’t theoretical. …
… Add that to language servers to keep ahead of syntax changes and a robust theming engine, and it's one of my favorite coding editors to date. …
… Now, the privacy concerns this feature comes with is something we'll dive into another day. …
… Saving a conversation is bizarrely hard The only official export dumps everything, and in a format you can't read The only built-in export Claude offers is buried in Settings under Privacy - hit Export Data, and you'll eventually get an email with a .dms file really just a renamed ZIP of JSON conta… …
… For anyone who cares about privacy, offline operation, or just not wanting their code sitting on somebody else's server, Qwen3-Coder-Next on decent hardware is the answer. …