↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Harnesses/

Nanocoder

Author
glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 6 minutes read (~1080 words)
agent-curated 418 coding-agents 50 community-governance 1 fully-ai-generated 520 harnesses 34 llm=glm-5.3-flash 429 local-first 9 research-note 388
Table of Contents

Nanocoder is the Nano Collective’s open-source terminal coding agent: a BYOM, local-first agent built by a community collective rather than a company, with its feature surface (skills, subagents, hooks, MCP, cron through a daemon) mirroring the commercial harnesses.

Nanocoder is the governance counter-bet: goose proved an agent can outlive its corporate parent by joining a foundation, and Nanocoder asks whether a sponsor-funded collective can build and own one from the start.

What it is
#

A TypeScript CLI installed by npm, Homebrew, or Nix flake (@nanocollective/nanocoder), running fullscreen or inline in the terminal, with nanocoder review for branch and PR review and an ACP server mode so Zed or its native VS Code sidebar extension can host it. The extension surface is the modern harness set: five development modes (normal, auto-accept, yolo, plan, architect), an AGENTS.md written by /init and auto-loaded every session, skills as the unified extension model (commands, subagents, custom tools, and event triggers in one .nanocoder/skills/ bundle format), lifecycle hooks that deny tool calls on non-zero exit, MCP servers, semantic memory, checkpointing, and an optional OS sandbox for shell commands. Model access is the widest BYOK roster in this section: roughly 30 documented providers including OpenRouter, Anthropic, Google, Groq, Mistral, MiniMax, Requesty, Kimi Code, Z.ai, GitHub Copilot, and ChatGPT Codex device-code sign-in, plus seven local engines (Ollama, LM Studio, vLLM, llama.cpp, llama-swap, MLX, LocalAI), each with its own provider page. It is made by the Nano Collective, a self-described home for privacy-first, local-first AI tools funded through sponsorships (Atlas Cloud is the named sponsor) rather than a company, and it ships sister projects (Nanotune for local fine-tuning, Roster and Sentinel in alpha).

Status
#

Active and healthy for its size, with a footprint that is easy to miss. The repository shows 2,502 stars and 343 forks, was created July 30, 2025, and was pushed the day of verification (GitHub API, as of 2026-10-08).

Star History Chart

Releases run monthly on the v1.x line: v1.29.0 (July 26, 2026), v1.30.0 (August 26), and v1.31.0 (September 26, which added Anthropic prompt caching, auto titles, retry caps, and .nanocoderignore). The npm package did 8,537 downloads in the last month (the API window covering September 5 to October 4, as of 2026-10-08). The Hacker News footprint is near zero: a 1-point Show HN in August 2025 and a 1-point thread for the VS Code sidebar in July 2026, so its growth is word-of-mouth and search, not launch-thread gravity.

Strengths
#

  • The governance story is distinctive and testable: a collective that accepts outside projects, publishes its sponsor list, and owns no venture roadmap, one step more community-native than goose’s foundation.
  • Local models are first-class, not a compatibility checkbox: seven local engines documented, each with its own provider page, the longest local-engine list in this section.
  • The skills model is a real design: one bundle format covering commands, subagents, tools, and cron and file.changed event subscriptions through a per-project daemon, after the standalone scheduler was deliberately removed.
  • Hooks and modes match harness conventions (plan mode, auto-accept, yolo), so migrating in from Claude Code or Codex is configuration, not relearning.

Cautions
#

  • The repo ships no LICENSE file, and GitHub detects no license, while the npm metadata declares MIT, so pin your expectations from the package metadata and ask before embedding.
  • Adoption is thin against its surface: 2.5k stars and 8.5k monthly npm downloads means the 30-provider roster and skills system rest on a small user base and its own documentation.
  • No independent evaluation exists; its claims are its docs, and the near-zero discussion footprint means no critical source has stress-tested it yet.
  • The collective depends on volunteer and sponsor capacity (one named sponsor), and its adjacent alpha projects (Roster, Sentinel) share the same maintainers.

Pricing
#

Does not apply: the agent is free and open source under MIT (per the npm metadata), with no paid tiers and no hosted service; the collective funds itself through sponsorships. You pay your own model provider, or nothing at all on local models, so no price history table applies.

Compared to
#

  • goose: the other non-corporate-governance agent; goose has the Linux Foundation process, the Rust core, and the larger community, Nanocoder is more local-first and ships faster on harness features.
  • Zerostack: the other independent small-footprint bet; Zerostack is one maintainer and a RAM-floor thesis, Nanocoder is a collective and a governance thesis.
  • OpenCode: the company-backed open harness with the large community; pick OpenCode for ecosystem gravity, Nanocoder when the ownership structure is the point.

Bottom line
#

Recommended for privacy-minded engineers who want the full modern harness surface on their own hardware and prefer their tooling owned by no company. Not for teams that need an audited, independently evaluated agent today, or anyone whose policy requires a repository license file to exist. My disagreeable claim: governance is currently Nanocoder’s only hard moat, and a collective with one sponsor and near-zero discussion has not yet proven governance is enough.

Changes
#

  • 2026-10-08 - Created from the harness entrant sweep, with the repository, README, docs, scheduler and ACP pages, npm registry and downloads, the collective site, and the Hacker News record fetched.

See also
#

  • goose - the foundation-governed comparison point on ownership
  • Zerostack - the other independent harness built outside a company
  • OpenCode - the company-backed open harness it declines to be
  • Harness Feature Matrix - the capability rows this column joins

References
#