NextClaw v0.59.3

This release combines long-conversation compaction and loading improvements with a fix for Windows session creation and imports failing with EPERM. Windows validation blocked runtime promotion of 0.59.2; upgrading from the previous runtime includes the improvements below.

Keep a recovery path when summaries fail

Empty, unfinished or oversized summaries are not treated as complete history. Compaction is deferred when the current context still fits. Required reductions save a recovery checkpoint and retain original records.

During recovery, the agent can read this conversation's history and ask for missing business conditions. Other tools remain paused until those conditions are explicitly confirmed, reducing repeated actions when previous outcomes are unclear. Ordinary chat and the agent claiming recovery do not clear this restriction. See Session management for channel confirmations.

Load large histories on demand

Opening a conversation reads a bounded page. Large messages show previews, with original content available one fragment at a time. Runtime context and idle session caches have capacity limits.

Older histories or damaged indexes show preparation progress with cancellation and retry. Initial preparation still scans original records and can take time for many small events. Once ready, normal pagination does not rescan the entire history.

Windows and upgrades

Windows session creation, snapshot imports and recovery now use the appropriate filesystem synchronization path. Source and recovery-intent files remain flushed, and ordinary file-write failures are reported.

npm install -g nextclaw@latest

This release ships through stable NPM and runtime update channels, retaining existing configuration and original journals. Older versions must not write conversations using the new recovery semantics; restore a complete snapshot with the current reader before rollback. New desktop installers are not included.