Are local models ready for coding agents?
HashiCorp’s founder takes the view that are not good enough yet. The counterargument is that have already been useful for coding for more than a year, as long as the task is narrow and clearly defined. The main divide is about how much freedom an should have inside a large codebase.
A local model running on a roughly $5,000 machine may handle focused work, but many commenters think it still cannot roam through a 50,000-line project with vague instructions the way a stronger cloud model like Opus 4.6 can. From a cost angle, local hardware can reduce token spending for heavy users, but the savings may disappear if weaker output slows people down. A practical middle ground is to let a cloud model plan and coordinate while handle smaller execution tasks.
Some teams make code more agent-friendly by splitting work into clearer modules and adding AGENTS.md-style guidance so smaller models know which files and rules matter.
Key points
- can be useful for focused coding tasks, but struggle more with broad, vague work in large projects.
- work better when the task scope and relevant files are clearly defined.
- A cloud model can coordinate work while handle smaller tasks to reduce token costs.
- Local hardware can pay off for heavy users, but lower quality can erase savings if it slows work down.
- AGENTS.md-style guidance and modular code can make smaller more practical.