NextClaw v0.59.2

Release status: NPM packages were published, but Windows installation validation found a directory-flush issue. This version was not promoted to the runtime channel. Use v0.59.3, which fixes this issue.

This patch improves context compaction reliability and loading performance for long conversations and very large messages.

Keep a recovery path when summaries fail

Empty, unfinished or oversized summaries are not treated as complete history. NextClaw defers compaction when the current context still fits. When context must shrink, it saves a recovery checkpoint and retains the 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.

Read 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 also have capacity limits.

The first open of an older history, or a damaged index, shows preparation progress with cancellation and retry. Preparation still scans the original records and can take time for many small events. Once ready, normal pagination does not rescan the entire history.

Upgrade and compatibility

npm install -g nextclaw@latest

Existing configuration and original journals are retained. NPM publication completed, while Windows validation blocked runtime promotion. Back up the data directory before upgrading if you need a rollback option. Older versions must not write conversations using the new recovery semantics; rollback requires a complete snapshot restored by the current reader first. This release does not include new desktop installers.