Nano-Collective/nanocoder

简体中文 繁體中文

An open coding agent for your terminal, built by a community collective rather than a company. Bring your own model, keep your code on your machine, and owe nothing to anyone.

Built by the Nano Collective, a community collective building AI tooling not for profit, but for the community. Nanocoder runs agentic coding on the model of your choice: local models via Ollama, or any OpenAI-compatible API such as OpenRouter, Requesty, Anthropic, and Google. You decide which provider runs your code and where your data goes. No closed-source features and no paid tiers gating the useful parts: privacy-respecting, local-first, and open for all.

npm install -g @nanocollective/nanocoder
nanocoder

Also available via Homebrew and Nix Flakes.

Specify provider, model, and starting mode directly:

# Non-interactive mode with specific provider/model
nanocoder --provider openrouter --model google/gemini-3.1-flash run "analyze src/app.ts"

# Interactive mode starting with specific provider
nanocoder --provider ollama --model llama3.1

# Flags can appear before or after 'run' command
nanocoder run --provider openrouter "refactor database module"

# Boot directly into a development mode (normal, auto-accept, yolo, plan, architect)
nanocoder --mode yolo
nanocoder --mode plan run "audit the auth module"

# Inline mode (native terminal scrollback) instead of the fullscreen default
nanocoder --no-alt-screen

# Review a branch or PR for bugs, security issues, and style violations
nanocoder review main
nanocoder review 42

# Open a PR in an isolated worktree for an interactive coding session
nanocoder worktree 42

Note: nanocoder review is diff-only v1 and requires an interactive terminal (TTY). It cannot be used with pipes or redirection and its output cannot currently be captured to a file — see #1287.

nanocoder worktree <PR-number> requires Git, an authenticated gh CLI, and an interactive terminal. It creates a sibling directory named <repository>-pr-<number>, checks out the PR head on a local nanocoder/pr-<number> branch, and starts Nanocoder there. The original working tree is left alone. Both the worktree and branch remain after Nanocoder exits; remove them with git worktree remove <path> and git branch -d nanocoder/pr-<number> when finished. An existing directory or branch is never reused or overwritten.

Nanocoder supports two rendering modes, mirroring what Claude Code and Codex ship:

• Fullscreen (default) — a fixed-height layout on the alternate screen buffer with in-app scrolling: PgUp/PgDn, with a scroll indicator and automatic snap-back to bottom on new output. Mouse reporting can be toggled with --mouse / --no-mouse or in preferences.
• Inline (--no-alt-screen flag, or "alternateScreen": false in preferences) — renders on the main screen; finished messages print once into the terminal's native scrollback, so your terminal's scrollbar, mouse wheel, and search work as usual. The transcript stays in the terminal after you exit.

In both modes, /clear fully resets the terminal to a fresh welcome banner, and exiting (Ctrl+C or /exit) erases the input UI cleanly instead of leaving a dead input box. Inline mode leaves the transcript in your scrollback; fullscreen mode restores the terminal to what it showed before Nanocoder started, so the transcript is not kept on screen (use /resume or /export to get it back).

Full documentation is available online at docs.nanocollective.org or in the docs/ folder:

• Getting Started - Installation, setup, and first steps
• Configuration - AI providers, MCP servers, preferences, logging, timeouts
• Features - Skills (commands, subagents, tools, event triggers), lifecycle hooks, the per-project daemon, checkpointing, development modes, task management, and more
• Commands Reference - Complete list of built-in slash commands
• Keyboard Shortcuts - Full shortcut reference
• Community - Contributing, Discord, and how to help

Nanocoder is built by the Nano Collective rather than a company, and that shapes the tool itself. There are no paid tiers, no telemetry quietly shipping your prompts somewhere, and no roadmap steered by what monetises best — the people building it are the people using it. Building in the open as a collective means the harness stays multi-provider on principle: you are never locked to one vendor's model, and the conventions, tests, and release standards are shared across every Nano Collective project so the work stays legible and contributable.

It is also bigger than one tool. The collective is assembling an open ecosystem of AI tooling — see the other projects — and contributors who show up now help shape what that becomes.

Nanocoder is built not for profit, but for the community, and that work is funded by sponsors. Become one.

The Nano Collective is a community collective building AI tooling for the community, not for profit. We'd love your help.

• Contribute: See CONTRIBUTING.md for development setup and guidelines.
• The collective: nanocollective.org · docs · GitHub · Discord
• Support the work: The Support page covers donations and sponsorship.
• Paid contribution: The Economics Charter sets out how scoped paid bounties work.