We updated the headline description of Nanocoder. This post explains why (the thinking behind the change, what the old framing was getting wrong, and what the new one gets right).
The short version
Before: "A local-first CLI coding agent..."
After: "A coding agent in your terminal, running on any model you choose (local models via Ollama, or any OpenAI-compatible API such as OpenRouter, Anthropic, and Google)."
The principles didn't change. The emphasis did, so the description matches both how the tool is actually used and why it exists at all.
What was wrong with the old framing
"Local-first" was the first thing you read about Nanocoder. It was the noun that defined the product. That created two problems.
Problem one: it reads as local-only. In practice, the Nanocoder harness is used heavily against cloud models (OpenRouter, Anthropic, Google, and more). "Local-first" as the headline undersold a significant part of what the tool actually is. Users who primarily used cloud providers felt like second-class citizens. Users who hadn't tried it assumed it didn't support their use case. Neither was true.
Problem two: it buried the real differentiator. The strongest thing about Nanocoder isn't that it's local. It's that it's built by a community collective, not a company. No paid tiers. No telemetry. No vendor lock-in. No investor-driven roadmap. The people building it are the people using it, and the direction is shaped by contributors rather than executives.
"Multi-provider on principle" is a consequence of being community-built. A collective has no commercial incentive to lock you to one vendor's model, so it doesn't. That story was getting crowded out by the local-first headline.
What "local-first" means in the collective's framing
This is not a retreat from local models. We support them. We prioritise them. We are actively investing in making them better (including through Nanotune, a separate project working to make small local models genuinely good at coding tasks).
The Nano Collective defines local-first as a spectrum: on-device by default, with privacy-preserving bridges to external capability when a task genuinely requires it. Supporting cloud providers doesn't violate local-first. The old copy implied a purity the tool never claimed.
The three collective principles are held together, in fixed order: privacy-respecting, local-first, open for all. The old copy elevated one of the three and dropped the other two. The new copy keeps all three, in order, as a description of the collective, and lets the product copy describe what the product does.
The honest position on local models today
Local coding models aren't yet at parity with the best cloud models for every task. We're working to close that gap. We don't oversell where it stands today.
Local-first is a direction we are committed to and investing in, not a limitation we impose on users today. Cloud support is how we stay useful while the local ecosystem catches up, and helping it catch up is part of the mission.
The differentiator that can't be copied
Features can be copied. The ownership model cannot.
Most AI tooling is built by companies whose incentives diverge from their users'. Nanocoder is built by the people who rely on it, in the open, under permissive licenses, with the direction shaped by contributors rather than investors.
That single fact (who builds it and why) is what shapes every other decision. No paid tiers, no telemetry, no vendor lock-in, no roadmap steered by what monetises best. Everything else flows from it.
This is why we lead with "built by a community collective" rather than "local-first". The community collective approach is the point.
Built by the Nano Collective. A community collective building AI tooling not for profit, but for the community.