Skip to content

NextClaw v0.59.10 ​

This release continues addressing Issue #73. New conversations could work while some older compacted conversations still failed with Invalid compacted message part boundary.

Keep original coordinates in partial message views ​

Large messages can exceed the working-window budget and load as partial previews. Some user-message previews were incorrectly treated as complete messages, making valid original part ranges appear corrupt. Partial views now retain their original coordinates and flags. Each preview part keeps its type and its share of the budget, so a large earlier text does not replace later parts with an archived string.

Older derived indexes rebuild automatically from the original journal. No conversation deletion or manual file editing is required. Original content is unchanged; oversized bodies remain available through paged history reads.

Separate summary failures from journal failures ​

Conversation summaries and context usage are derived calculations. If they fail after the journal has been written, the failure is diagnosed separately and retried on a later update. It no longer locks a successfully written conversation as a journal-write failure. Actual storage failures still stop execution to prevent unsaved work.

Validation includes valid source journals, partial previews, old-index upgrades, cold continuation, and a real model reading unknown random values, observing SHA256 stdout, and writing reports. The reporter's original session files are unavailable, so this does not establish every trigger on that machine. The initial 0.59.1 incident remains under investigation, and content never written to disk cannot be recovered by this release.

Released under the MIT License.