NextClaw v0.59.6
This release shipped conversation save-failure protection through stable NPM, the Runtime update channel, and Desktop installers. See v0.59.7 for subsequent fixes to incorrect session locking and recovery. The first trigger on the reporting machine in Issue #73 remains under investigation.
Stop when conversation history cannot be saved
It includes the 0.59.5 fix: a write failure stops the affected run, reports the original cause, and clears pending inputs without repeated log flooding. Permission and I/O read failures are no longer treated as missing sessions. Saved history is retained; content that was never successfully written cannot be recovered by this fix.
Include history resources for older Desktop hosts
Runtime bundles now include the platform libSQL native resource so older Desktop hosts without built-in SQLite can prepare and read history indexes. Desktop installation and cold-start upgrades undergo automated validation.
Upgrade the CLI with npm install -g nextclaw@latest. See When conversation history cannot be saved for storage recovery steps.