Repository navigation
Nanocoder v1.26.0 is out. Here is what changed and why it matters. #43
will-lamerton
announced in
Nanocoder
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Nano mode: a leaner prompt for low-end hardware
The
/tunecommand now offers a third tool profile called nano mode. It is strictly more aggressive than minimal: it dropsfind_files,list_directory, andagentfrom the tool set; trimsCORE PRINCIPLESandCODING PRACTICESsections; uses 4-line-or-lessTASK APPROACH,FILE OPERATIONS, andCONSTRAINTSblocks; and replaces the verboseSYSTEM INFORMATIONblock with a single-line## SYSTEMnote.The result is a system prompt of roughly 150-250 tokens, compared to 500-700 in minimal mode. That difference matters when you are running a 1B or 3B parameter model on a machine with limited VRAM or RAM.
Nano mode ships with a "Nano (low-end hardware)" preset and an Include AGENTS.md toggle so you can opt back in if your setup handles it.
Reasoning traces, live
Nanocoder now streams reasoning content from models that emit it, such as Codex GPT-5, DeepSeek-R1-style models, Anthropic extended thinking, and similar. It renders as a collapsible Thought block above the response, persists across the conversation history, and appears in logs.
Toggle expansion with
Control+R. Set the default via the new Display Settings panel (/settings→ "Tool Results and Thinking"). Pin it per-session from the tune menu using theexpandedReasoningoption.Control+Ralso works for reasoning trace follow-ups, and the system ensures reasoning content survives correctly across the full conversation lifecycle.Non-interactive
--plainflagA new
--plainflag streams output without Ink rendering, making it safe for CI pipelines, shell scripts, and programmatic pipes. Exit codes are deterministic, stdin and stdout are handled cleanly, and there are no interactive prompts.VS Code extension rework
The "Ask Nanocoder" command is gone. Instead, highlighted text and the currently focused file are automatically pulled into Nanocoder as context, a more natural interaction model. The extension protocol and entrypoint have been rewritten, and the development mode indicator and chat input hooks are tighter.
Other additions
/rename— rename the current chat session. Reflected in the development mode indicator.defaultMode— set a starting mode (normal,auto-accept,yolo,plan) inagents.config.jsonso you do not always launch in normal mode.agents.config.json. Define a project-level prompt that augments or replaces built-in sections.contextWindowandcontextWindows[model]. Resolution order: session override (/context-max,--context-max) → provider model override → provider default →NANOCODER_CONTEXT_LIMIT→ fallback./usage, status bar, auto-compact, and context reporting all use the active provider config.disabledTools— disable specific built-in tools project-wide, honoured by both main agent and subagents.--trust-directory— bypass the first-run directory trust prompt for automation. Yolo mode already skips the validator.<function=...>format support in the tool-call parser.nanocoder-preferences.json.Toolchain and configuration updates
engines.node.packageManagerfield pins the pnpm version automatically for contributors and CI.pnpm-workspace.yamlreplacespackage.json-based pnpm config. All 16 version overrides were removed — every one was redundant under current dependency resolution.Fixes
lastProviderstate is now correct after running the config wizard mid-session.@mentionautocomplete work cross-platform on Windows.MCPTool.inputSchematyped asJSONSchema7with anisPlainObjectguard at the protocol boundary.caCertPathTLS configuration now applies to Anthropic and Google providers.git_prtool no longer requires approval in yolo mode.Dependency updates
ai6.0.116 → 6.0.174,@ai-sdk/openai3.0.41 → 3.0.53,@ai-sdk/google3.0.53 → 3.0.64,@ai-sdk/openai-compatible2.0.35 → 2.0.41,undici8.0.2 → 8.2.0,react19.2.4 → 19.2.6,yaml2.8.3 → 2.8.4,dotenv17.3.1 → 17.4.2,@nanocollective/get-md1.3.0 → 1.3.1, plus dev-dependency bumps.Breaking change
nanocoderTools.alwaysAllowhas been removed. It duplicated the top-levelalwaysAllowwith no extra behaviour. Move any entries fromnanocoderTools.alwaysAllowto the top-levelalwaysAllowarray inagents.config.json. The deprecatedagents.config.example.jsonhas also been removed.Built by the Nano Collective — a community collective building AI tooling not for profit, but for the community.
https://github.com/Nano-Collective/nanocoder
All reactions