Evidence record / gemini-cli

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-gemini-cli-stable-v0-64-0-appends-session-patches-and-serializes-local-writes

Stable v0.64.0 appends session patches and serializes local writes. Stable 0.64.0 appends $patch records instead of repeatedly rewriting the complete message list. Its recording service limits cachedConversation.messages to the last 50 messages, not every in-memory history copy; full history is reconstructable from disk. Edit/write operations and shadow-repository checkpoint snapshots use in-process path locks, and file writes use a sibling temporary file and rename. This is not cross-process locking. CLI persistent state gains atomic writes/backup recovery, and the headless UI receives the resolved folder-trust state. The PR author’s 8.2-million-character/400-MB example is an attributed measurement, not a verifier benchmark.

Channel: tagged-release. Half: both. Date: 2026-10-13.

Operator consequence: Update session readers to apply $patch before adopting 0.64.0; old $set-only readers can miss changed tool results. Prefer its write/checkpoint serialization within one process, but coordinate separate agent processes yourself. Inspect the full on-disk record when a cached history view is insufficient.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-gemini-cli-stable-v0-64-0-appends-session-patches-and-serializes-local-writes

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact