Getting started¶

Install¶

nanocode supports macOS and Linux only
Python 3.11 or newer
uv to install and run

uv tool install nanocode-cli

Upgrade¶

uv tool upgrade nanocode-cli

nanocode checks PyPI at most once a day and reports an available update at startup and in /status.

Configure¶

nanocode needs one thing to start: a provider to talk to. Generate a starter config:

nanocode --init-config

This writes ~/.nanocode/config.toml. Only the [provider] block is required; every other setting has a built-in default, and the file lists the common ones as comments.

Point it at a provider¶

nanocode speaks to any OpenAI-compatible API (and to Anthropic). Open the config and fill in a provider — for example DeepSeek:

[provider]
active = "default"

[provider.default]
url = "https://api.deepseek.com"
key = "sk-..."
model = "deepseek-v4-flash"

Key	Meaning
`url`	Base URL of the API
`key`	Your API key
`model`	Model name to use

You can define several [provider.<name>] blocks and switch between them with active (or /provider inside a session). See Configuration for every option, including reasoning effort and per-host tuning.

Start a session¶

nanocode

Type a request in plain language and the agent starts working — reading files, proposing edits, running commands. Before anything that changes files or runs a command, it asks for confirmation (unless you pass --yolo). You can keep typing while it works; see Follow-ups.

Exit with /exit, /quit, or Ctrl-D.

Command-line flags¶

Flag	Effect
`-c`, `--last`, `--latest`	Resume the most recent session in this project
`--resume [UID]`	Resume a saved session; with no `UID`, resumes the latest
`--yolo`	Skip confirmation prompts for mutating tools
`--theme {auto,light,dark}`	Override the configured terminal color theme
`--config <path>`	Use a specific config file instead of `~/.nanocode/config.toml`
`--init-config`	Write a starter config file and exit
`-h`, `--help`	Show command-line help and exit
`-v`, `--version`	Print the version and exit