nanoai-cli
v1.1.8
Published
Terminal UI, ACP server, and automation-friendly CLI for NanoAgent.
Downloads
1,226
Maintainers
Readme
nanoai-cli
nanoai-cli installs the NanoAgent CLI as the nanoai command.
NanoAgent is a local AI coding agent for terminal workflows, ACP-compatible editors, and automation. This npm package is a thin installer: it downloads the matching self-contained NanoAgent release for your platform, verifies it against the published SHA256SUMS, and launches it without requiring a .NET toolchain.
Why use this package
- Install NanoAgent with
npm,pnpm, orbun. - Download the correct native binary for the current platform automatically.
- Verify release archives before extraction with published SHA-256 checksums.
- Recover automatically on first run if
postinstallwas skipped or the binary is missing. - Toggle a built-in git sidebar (F7) showing branch, queued prompts, recent commits, and changed files as
filename (relative/path)— click a file to open it in your editor, and useAlt+S/Alt+P/Alt+O/Alt+D/Alt+C/Alt+Bfor stage, pull, push, discard, commit, and branch actions.
Install
npm install -g nanoai-cli
# or
pnpm add -g nanoai-cli
# or
bun add -g nanoai-cliStart NanoAgent:
nanoaiIf you want a quick non-interactive smoke test after install:
nanoai --versionHow installation works
On install, the package tries to:
- Resolve the correct release asset for the current OS and CPU architecture.
- Download the matching
NanoAgent.CLI-<rid>.ziparchive from GitHub Releases. - Download
SHA256SUMSfrom the same release. - Verify the archive checksum before extraction.
- Extract the NanoAgent binary into the package's
vendor/directory.
If the download is skipped or fails during postinstall, installation still succeeds. The launcher downloads the binary automatically the first time you run nanoai.
bun note
bun add skips postinstall scripts by default, so the binary is usually downloaded on first launch instead of during installation.
To fetch it eagerly after installing with bun, run:
bunx nanoai-cli --versionSupported platforms
| OS | Architectures | | --- | --- | | Windows | x64 | | macOS | x64, arm64 | | Linux | x64, arm64 |
Updates
By default, the package downloads the release tag that matches the npm package version, using v<package-version>.
At runtime, the launcher can also check GitHub for a newer NanoAgent release. When running interactively, it prompts before replacing the installed binary with the latest release and then continues launch.
Skip the runtime update prompt with either:
nanoai --no-update-checkor:
NANOAGENT_SKIP_UPDATE_CHECK=1 nanoaiEnvironment variables
| Variable | Purpose |
| --- | --- |
| NANOAGENT_SKIP_DOWNLOAD | Set to 1 to skip the install-time download. The binary will still be fetched on first run. |
| NANOAGENT_TELEMETRY_DISABLED | Set to 1 to opt out of the anonymous nanoagent cli installed analytics event. DO_NOT_TRACK=1 is also honored. |
| NANOAGENT_SKIP_UPDATE_CHECK | Set to 1 to disable the runtime check for newer GitHub releases. |
| NANOAGENT_CLI_TAG | Override the release tag to download, such as v1.2.3. |
| NANOAGENT_CLI_VERSION | Override the version used to derive the default release tag. |
| NANOAGENT_CLI_BASE_URL | Override the release asset base URL for mirrors, testing, or private distribution. |
Manual reinstall
If you need to force a fresh binary download for a local install, run:
node ./node_modules/nanoai-cli/scripts/download.jsIf the package was installed globally, reinstalling the package is usually the simplest way to refresh the bundled launcher files.
Learn more
- Product overview: NanoAgent README
- Full documentation: docs/documentation.md
- Releases: GitHub Releases
- Issues: GitHub Issues
License
Apache-2.0
