2026-08-14 · NextClaw v0.36.1
Published: 2026-08-14 Tags: release npm patch
NextClaw v0.36.1 fixes a case where commands could keep using the previous version after an in-app update. Once the page reconnects, agents, service restarts, and newly opened nextclaw commands all use the current runtime instead of splitting between old and new versions.
Fixes
- Commands stay aligned after updates: When an agent runs
nextclawduring a task, it uses the same version as the current page. - Service restarts stay on the current runtime: Background services, autostart, and post-update lifecycle operations no longer fall back to the previous app.
- One update is enough: Download and apply the update from the page as before. No second global installation is required after reconnecting.
Defaults and compatibility
- The stable launcher continues to select updates, handle rollback, and reject incompatible runtimes. Existing update entry points do not change.
- The global npm package may be older than the current runtime;
nextclaw --versionnow reports and runs the current runtime version.
Learn more: NextClaw v0.36.0