NanoClaw changelog: what's new each month
Every stable NanoClaw release summarised by month: the highlights, new features, improvements, fixes and anything you need to act on. 5 months covered; the current month updates daily.
October 2026
1 release: 2026.10.0
October brought security updates, improved proxy handling, and better visibility into what's happening during failures. The release channels system now lets you control update timing across your installations.
- OneCLI installs must upgrade the OneCLI gateway to exactly 1.42.0.
- Iron Proxy installs must rerun the Iron setup after updating to rebuild the proxy.
- /update-nanoclaw now installs the newest release instead of the tip of main; control this with NANOCLAW_UPDATE_CHANNEL in .env.
Highlights
- OneCLI gateway users must upgrade to 1.42.0 to close a credential-injection security bypass.
- Update channels let you choose stable, beta, or edge per installation, with tracking in upgrade-state.json.
- Failed Claude runs now show clear error messages telling you what went wrong and who can fix it.
- Keyless models can now reach Iron Proxy over plain HTTP on the same machine.
- The service respects standard outbound proxy environment variables for internet access.
New
- Update channels system with stable, beta, and edge options configurable per install.
- Outbound proxy support via HTTPS_PROXY, HTTP_PROXY, ALL_PROXY, and NO_PROXY environment variables.
- Keyless model access to Iron Proxy over plain HTTP.
- Uncredentialed read bypass for GET and HEAD requests with no body when NANOCLAW_GATEWAY_UNCREDENTIALED_READS is enabled.
Improved
- Claude failure messages now display concisely with actionable guidance on who can fix the issue.
- Iron Proxy certificate handling regenerates expired certificates on upgrade.
- Iron Proxy host rules now match case-insensitively.
- Update system records channel and release version in data/upgrade-state.json for support visibility.
Fixed
- OneCLI gateway credential-injection vulnerability (requires upgrade to 1.42.0).
- Iron Proxy upstream compatibility updated to v0.52.0.
September 2026
1 release: 2.4.0
September brought significant model defaults and infrastructure changes to NanoClaw, with new credential and proxy options and improvements to container management during updates.
- Custom sources composing agent instructions must migrate to new module system.
- Credential gateways must be installed before restart when merging upstream by hand.
- OpenCode skill requires payload refresh; re-run /add-opencode to use native provider contracts.
Highlights
- Claude agent groups now default to Opus 5.5 model instead of previous versions, affecting costs and usage limits.
- New Iron Proxy option provides local gateway with control console for secrets, credentials, and OAuth management.
- Custom instruction sources must migrate to the new module system for continued compatibility.
- Agent containers are now properly stopped during updates, eliminating timeout issues.
New
- Iron Proxy installed via /add-iron-proxy for local gateway with Iron Control web console.
- Credential gateways now available through skills system with /add-onecli for OneCLI support.
- Claude agents now default to Concise output tone.
- Codex groups default to gpt-6-astra for new threads.
Improved
- Update process now stops idle agent containers with 10-second grace period instead of timing out.
- Claude model defaults upgraded: API-key installs from Opus 5, Pro and Team Standard from Sonnet.
- Codex skill now uses native provider contracts with updated payload requirements.
Fixed
- Agent updates no longer time out when idle containers are running.
August 2026
3 releases: 2.1.54 → 2.3.0
August brought major architectural changes to NanoClaw, unifying how channels, memory, and plugins work across the system. The release focused on simplifying integrations, tightening security, and improving session management.
- iMessage unified into single channel with /add-imessage backend selection required.
- All providers now use shared OKF v0.1-compatible memory tree; persona moves to instructions.prepend.md.
- Channel install skills become source of truth; whatsapp-formatting and slack-formatting move to channels branch.
- Scheduled tasks moved from MCP tools to ncl tasks; task delivery now requires explicit named destination.
Highlights
- iMessage now supports both local and hosted backends through a single unified channel.
- All providers now share one memory format, with persona configuration moved to instructions.
- Agent templates are now first-class plugins with standardized plugin.json and mcp.json files.
- New per-agent Slack apps for classic Slack installs, with agent spawning directly from Slack.
- Host restarts now preserve running agent sessions instead of killing in-flight work.
New
- Default provider setting for new agent groups via DEFAULTAGENTPROVIDER.
- Unified guard system for all privileged actions crossing container or channel boundaries.
- Task management moved to ncl commands with explicit delivery destinations.
- Remote MCP servers can now be registered via HTTP with Streamable support.
- Plugin MCP servers can declare working directories in mcp.json.
- Agent-to-agent messaging now properly prioritizes over Claude Code's built-in SendMessage.
- Container identity explicitly configured for non-root hosts with uid and HOME settings.
- Template-based agent creation in the setup wizard with local or remote templates.
Improved
- Channel install skills now follow deterministic /add-channel patterns for consistency.
- In-place plugin updates when applying a template to groups that already have it.
- Scheduled task lifecycle now stricter with cascade deletion and due-run rejection.
- Container gateway wiring is now typed and admission-checked before validation.
- Agent-to-agent messaging receives proper session driver support.
- MCP servers support configurable working directories via ${PLUGINROOT} paths.
Fixed
- Codex provider updated to pin @openai/codex 0.146.0 ahead of GPT-5.4 retirement.
- Claude installs updated to use hardened agent image with patched sandbox components.
- Session data preservation ensured when switching from custom mailbox implementations to built-in SQLite.
- Slack experience now properly handles agent spawning in classic single-bot installs.
June 2026
2 releases: 2.1.0 → 2.1.17
June brought major provider flexibility and reliability improvements to NanoClaw. The release adds support for multiple AI providers, fixes critical data corruption issues, and streamlines group management with cascading deletions.
- Startup requires upgrade-state.json marker; install must reach current version through sanctioned setup path.
- OneCLI SDK 0.5.0 → 2.2.1 requires OneCLI server with /v1 API; older servers will 404.
- Provider selection is now explicit per group; no install-wide default provider exists.
Highlights
- New Codex (OpenAI) agent provider option alongside Claude, selectable per group with full runtime support.
- Groups now support provider-specific memory isolation, allowing seamless switching between Claude and Codex without stale data.
- Cascading group deletion now cleanly removes all associated sessions, tasks, and messages in a single transaction.
- Long-lived session transcripts now auto-rotate at 12 MB to prevent size-related issues.
- Billing errors and access denials now properly reach users instead of silently failing.
New
- Codex (OpenAI) agent provider with full planning, MCP tools, and server-side history support.
- Setup wizard can now select, install, and authenticate non-default agent providers.
- /add-rtk skill installs rtk into agent containers with output-summarizing proxy, reducing token usage by 60–90%.
- WhatsApp-formatting container skill adds @mention syntax support for agent communication.
- /migrate-memory command enables cross-provider memory transfer without runtime involvement.
- /upload-trace command ships session transcripts to Hugging Face.
- /update-nanoclaw automatically upgrades the OneCLI gateway alongside SDK updates.
- Provider registry in setup picker for streamlined provider selection and installation.
Improved
- Startup now validates upgrade state to ensure sanctioned installation paths.
- Long-lived hub sessions rotate transcripts before resume to maintain performance.
- Group deletion now cascades across sessions, destinations, members, wirings, and scheduled tasks in one transaction.
- Persistent inbound.db corruption now triggers container exit for host-sweep respawn with fresh mount.
- Provider choice is now explicit per group via ncl groups config, removing install-wide defaults.
- OneCLI SDK upgraded to 2.2.1 with pinned gateway and CLI versions in versions.json.
Fixed
- Multiple pending messages no longer trigger N>1 retry loops after outbound <messages> envelope removal.
- Command-gate denials now properly reach senders instead of silencing with SQLITEREADONLY errors.
- Budget and billing-exhausted errors now surface to users instead of being silently dropped.
- Session transcript retry logic fixed for pending messages bundled in envelope format.
May 2026
2 releases: 2.0.63 → 2.0.64
May brought security hardening, service isolation improvements, and fixes for credential handling and message delivery. The month focused on closing access control gaps and aligning integrations with the v2 architecture.
- Service names changed: launchd labels now use com.nanoclaw.<sha1(projectRoot)[:8]> format and systemd units use nanoclaw-<slug>.service format
- Gmail and Google Calendar tool setup no longer supports TOOLALLOWLIST edits or container.json writes; use DB-backed mounts instead
Highlights
- Service names are now per-install, using project-specific identifiers to isolate NanoClaw instances.
- MCP servers now properly inherit OneCLI gateway routing, fixing repeated credential requests after installation.
- Destination changes in the approval flow now reach receiving agents immediately.
- CLI scope validation now fails closed when scope is missing, preventing cross-group access.
- Message wrapping enforcement strengthened to prevent output truncation.
New
- Per-install service naming with SHA1-based slugs for launchd and systemd units.
- Slack scope checklist now includes files:read and files:write permissions for attachment handling.
Improved
- Compaction destination reminder placement moved to end of summary to avoid truncation.
- Gmail and Google Calendar skills updated to use v2 container-config model with DB-backed mounts.
- Poll loop now nudges agent output to ensure message wrapping compliance.
- Session get operations guarded against cross-group oracle access.
- Core CLAUDE.md instructions now require message wrapping for all outputs.
Fixed
- OneCLI credentials no longer repeatedly requested after MCP server installation.
- Approved destinations now properly projected into receiving agent's local session state.
- Scope field validation closed to prevent missing scope errors.
- Repository rename references cleaned up across code, docs, and CI workflows.
Summaries are written automatically from the official release notes (full changelog ↗); check the original notes before relying on a detail. NanoClaw: pricing, features and alternatives · All changelogs