NanoAgent

Your local AI coding agent for desktop, terminal, and editor workflows.

Build Tests Release License Version Stars Issues Downloads Forks

View NanoAgent releases Install NanoAgent VSCode Install NanoAgent CLI Install NanoAgent Desktop Install NanoAgent VS Install NanoAgent Nuget

NanoAgent gives developers an AI teammate that can work inside a real repository while keeping the human in control. Ask it to understand a codebase, plan a change, edit files, run validation, review a diff, or automate a pull request review from the same toolchain you already use.

It is built for practical engineering work: local projects, real shells, version-controlled memory, reviewable changes, and explicit approval for sensitive actions.

• What You Can Do
• Product Surfaces
• Built For Control
• Get Started
• Quick Start
• Provider Choice
• Benchmarks
• Telemetry
• Documentation
• Contributing
• Support
• License

• Understand unfamiliar code faster with repository-aware search, summaries, and focused file inspection.
• Turn feature requests and bug reports into planned, editable, testable changes.
• Run code review with a findings-first workflow for local diffs, files, pull requests, and merge requests.
• Switch between hands-on implementation, read-only planning, and read-only review profiles.
• Keep team knowledge in reviewable .nanoagent/memory files instead of hidden agent notes.
• Save repeatable slash prompts in .nanoagent/commands and run them from the terminal, desktop app, or editor.
• Use the provider that fits your budget and policy, from API-key providers to subscription sign-in and local Ollama.
• Bring the same agent into desktop, terminal, VS Code, ACP-compatible editors, and CI review automation.

Use the desktop app for a visual workspace with chat, model controls, profile switching, budget controls, permission prompts, activity output, and undo/redo for tracked file edits.

Use nanoai when you want a keyboard-first agent for interactive work, one-shot prompts, piped input, quick reviews, and automation-friendly output.

Use the VS Code extension to chat with NanoAgent, send selections, review files, review Git diffs, and apply suggested changes from inside the editor.

Use the Visual Studio extension to keep a NanoAgent tool window inside Visual Studio while driving the local NanoAgent CLI over ACP.

Use the included GitHub Actions, GitLab CI, and Bitbucket Pipelines examples to run NanoAgent against pull request and merge request diffs, then post review comments back to your platform.

NanoAgent is designed for useful automation without silent surprises.

• Profiles separate implementation, planning, review, exploration, and delegated work.
• Permission rules decide what can run automatically, what asks first, and what is denied.
• Sensitive actions can require approval, including file edits, shell commands, network access, MCP tools, memory writes, and elevated operations.
• Tracked file edits can be undone and redone.
• Secret redaction is off by default; when enabled, secret-looking values are redacted before logs, memory, audit records, and displayed tool output.
• Your workspace stays local; prompts and selected context are sent only to the model provider you configure when needed for a request.

Download the latest desktop build from GitHub Releases, or install the CLI:

Release assets also publish SHA256SUMS and GitHub artifact attestations so you can verify both checksums and build provenance.

Install with the release installer.

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/rizwan3d/NanoAgent/master/scripts/install.sh | bash

Windows PowerShell:

irm https://raw.githubusercontent.com/rizwan3d/NanoAgent/master/scripts/install.ps1 | iex

Then start NanoAgent:

nanoai

The CLI is distributed only through the release installers above; the tag-based release workflows publish just the NanoAgent library to NuGet.org.

On first launch, NanoAgent walks you through provider setup: pick a subscription account, API-key provider, OpenAI-compatible endpoint, or a local provider, then let it discover available models. After that you are ready to work.

Start an interactive session in your repository:

nanoai

Run a single prompt and print the response:

nanoai "Find risky changes in this branch"

Pipe context in from another command:

git diff --stat | nanoai --stdin --profile review

Resume where you left off (NanoAgent prints a resume command when you exit):

nanoai --session <session-guid>

Once inside a session, common commands include:

Save your own repeatable prompts as .nanoagent/commands/*.md and run them as slash commands. See the full documentation for the complete command, profile, and configuration reference.

NanoAgent supports OpenAI, ChatGPT Plus/Pro sign-in, Anthropic Claude Pro/Max sign-in, GitHub Copilot sign-in, OpenRouter, Kilo Code, Cerebras, Groq, DeepSeek, Anthropic, Google AI Studio, Ollama, LM Studio, Ollama Cloud, and OpenAI-compatible providers.

NanoAgent includes task-based benchmarks in benchmarks/ so we can measure real coding-agent behavior, not just chat-style answers. The benchmark suites currently cover bug fixing, repository understanding, patch quality, security review, tool safety, and a regression bundle that reruns the same tasks over time.

Tasks are defined in benchmarks/tasks/ and grouped by benchmarks/manifest.json. Each task can score the agent with response checks, validation commands, and diff constraints against small local fixtures or this repository itself.

Run the full benchmark set locally with:

python benchmarks/scripts/run_benchmarks.py --all --system --skip-preflight

Run the regression-only suite with:

python benchmarks/scripts/run_benchmarks.py --suite regression --system --skip-preflight

Generated summaries are refreshed in benchmarks/results/latest.md and benchmarks/results/latest.json.

NanoAgent sends anonymous product analytics to PostHog using built-in US Cloud defaults in code. You can still override Application:Telemetry:* settings, and /disableanalytics writes Application.Telemetry.Enabled=false to .nanoagent/agent-profile.json for the current workspace.

Collected:

• NanoAgent version
• OS family
• app surface such as CLI, Desktop, VS Code, Visual Studio, JetBrains, GitHub Actions, GitLab CI, or Bitbucket Pipelines
• execution environment (local or ci)
• CI provider when detected (github_actions, gitlab_ci, bitbucket_pipelines, or generic CI)
• feature names used
• success and failure counts
• token and duration buckets
• daily runs and usage-time buckets

Never collected:

• prompts
• source code
• file paths
• repository names or URLs
• API keys
• terminal output

The technical guide lives in docs/documentation.md. It covers installation details, first-run onboarding, desktop and terminal workflows, VS Code and Visual Studio setup, ACP integration, CI review automation, codebase indexing, providers, permissions, MCP, memory, hooks, troubleshooting, release automation, and source builds.

Contributions are welcome. To work on NanoAgent from source:

1. Fork and clone the repository.

2. Restore, build, and run the CLI:

   dotnet restore NanoAgent.CrossPlatform.slnx
   dotnet build NanoAgent.CrossPlatform.slnx
   dotnet run --project NanoAgent.CLI/NanoAgent.CLI.csproj

3. Run the test suite before opening a pull request:

   dotnet test NanoAgent.Tests/NanoAgent.Tests.csproj

Open an issue to report bugs or propose features, and keep pull requests focused with a clear description of the change. See docs/documentation.md for full source-build details.

• Browse the documentation for setup, workflows, and troubleshooting.
• Report bugs or request features via GitHub Issues.
• Find the latest builds on the Releases page.

Apache License 2.0. See LICENSE.txt.

Sponsored by
ALFAIN Technologies (PVT) Limited