Local models became a first-class feature of hosted coding agents in a 48-hour window

Three moves, two days, no coordination between them.

August 10–11: GitHub shipped Ollama as a BYOK provider inside Copilot for JetBrains (GitHub Changelog). Unsloth released Unsloth Desktop with a command literally named unsloth start claude, which points Claude Code and Codex at models served on your own hardware (Unsloth Docs). Meta released Muse Glimmer 30B under Apache 2.0, benchmarked on MCP-Atlas and SWE-Bench rather than chat evals. And NVIDIA rewrote Switchyard from Python to Rust in a 193-commit v0.2.0 that translates between OpenAI Chat Completions, OpenAI Responses, and Anthropic Messages so Claude Code can talk to vLLM, NIM, or Ollama (GitHub).

The Unsloth thread was the biggest r/LocalLLaMA post of the day at 1,159 upvotes and 314 comments. The ggml-org crew put up llama.app the same week, a plain-English landing page pitching llama.cpp to people who don't know what llama.cpp is, and it took 297 points on HN (llama.app). The repo's at 123.5K stars.

Here's what changed, and it's subtle. The local model story used to be "run a chat model offline." That's a hobby. What shipped this week is "swap the inference backend under an agent harness you already know how to drive." That's an ops decision. Your prompts, your skills, your MCP servers, your muscle memory all stay put. The provider config changes.

I've been running everything through the subscription tier and watching quota like a hawk. What makes this actually usable now is the third leg: the trycua team published a Metal capability shim for macOS VMs that lies about exactly two values, reporting Apple GPU family 9 instead of 5 and 64 KB instead of 32 KB max threadgroup memory, which unlocks SIMD-group matrix and bfloat16 kernels in llama.cpp (trycua/cua). TinyLlama 1.1B went from 12.63 to 206.60 tok/s. Gemma 4 12B from 3.41 to 49.67. Muse Glimmer 30B from 2.38 to 21.08. That's 8.87x on the big one, 16.36x on the small one, on an M1 Ultra host. 297 points on HN.

Thirty lines of shim. 16x.

What to do: don't rip out your hosted setup. Do build the fallback path now, while it's cheap. Point one non-critical agent role at a local backend through Switchyard or Unsloth Desktop and see what breaks. My bet is that tool-calling reliability, not raw quality, is what fails first, and you want to find that out on a code-review agent, not on the thing that ships to prod. The routing story is real too, NVIDIA's Nemotron 3.5 Lightning is a 30B MoE explicitly built for the narrow high-volume roles inside multi-agent systems, and NVIDIA claims Switchyard routing gets frontier-level accuracy at roughly a third the task cost of running Opus 4.8 for everything (NVIDIA). That number is vendor-authored, so discount it. The architecture is still right: tier your model per role.

Switchyard is labeled pre-alpha, "not for production use," and took ~370 stars in one day. Treat it as a preview of where every harness ends up, not as something to depend on this quarter.