Skip to content

NextClaw v0.59.5 ​

This release fixes sessions continuing to run after journal writes fail, addressing Issue #73.

Stop when history cannot be saved ​

When a session cannot save its history, the affected run stops, the interface receives an explicit storage error, and pending queued inputs are cleared. Other healthy sessions can keep working. Diagnostics retain the first underlying filesystem error without repeatedly flooding the log.

After fixing disk space, directory permissions, or file access, restart NextClaw and resend unfinished requests. Previously saved records are preserved; this fix cannot recover content that was never successfully written.

Distinguish unreadable history from missing history ​

An existing session that cannot be read because of permissions or an I/O failure now reports the error instead of appearing to be missing.

0.59.5 was released to NPM first; 0.59.6 delivers the complete Desktop installers and stable update channels. CLI users can upgrade with npm install -g nextclaw@latest. See When conversation history cannot be saved.

Released under the MIT License.