AIClaw

AIClaw's SHA256SUMS.txt format is "digest + two spaces + filename" per line, originating from the GNU coreutils sha256sum tool.

The installer replaces the application files, but settings, chat history, global application data, and memory keep their original user data locations; the installer does not move them into the program folder.

AIClaw's smoke test script installs to a temporary path containing spaces on a Windows runner, checks the application files, modifies the program files into a stale fixture and reinstalls to verify replacement, and places sentinel files in two user data locations to check data retention after install, reinstall, and uninstall.

AIClaw's current installer has no Authenticode signature, so Windows may show an unknown publisher warning.

AIClaw's checksum comparison only verifies that the downloaded file matches the digest provided by the release; it does not independently prove the publisher's identity, and the real trust anchor is the release channel (the GitHub Release page) itself.

For existing ZIP users, migrating to the installer version requires manually downloading the setup executable and installing it, and the old extracted directory will not be deleted automatically.

AIClaw's installer build script (scripts/package-win-installer.mjs) consumes the Windows application directory produced by the existing packager, reads the application version and passes it to electron-builder's NSIS target, and is configured to disable installation directory selection and to set deleteAppDataOnUninstall=false.

AIClaw v3.7.15's update process consists of four steps: check the latest GitHub Release, download the Windows installer to a temporary directory, download SHA256SUMS.txt and compare digests, and ask Windows to open the installer and exit the application.

AIClaw's updater does not pass a silent install flag, and its definition of "success" is that the installer has been launched rather than that installation has completed.

When a checksum entry is missing or the digest does not match, AIClaw does not open the installer, and the application keeps running.

AIClaw's updater refuses to install from development mode; a release with only a ZIP falls back to the previous "download and open folder" behavior.

AIClaw's preview state store maintains an array of file previews and a separate active selection, and opening a file that already exists in the current session reuses its tab and cached content.

When the same file is opened again, AIClaw does not refresh it from disk; when a file needs to be reread, Refresh should be used; Compare, meanwhile, looks up the file's most recent change record in the session it belongs to.

For normal windows, AIClaw's Electron host process attempts to add up to 640 pixels of width, with the upper limit constrained by the current display's available area.

AIClaw's app layout places the reader beside the chat window, the chat stays mounted at all times, and the reading area independently displays the currently selected file.

AIClaw's desktop smoke tests use the real Vue/preload interface together with fixture host responses, covering scenarios such as tab reuse not triggering extra reads, restoring scroll position, preserving unified diff, keyboard switching, and background completion not changing the selection.

AIClaw's state store assigns a request identifier to each read, and when the read completes it checks whether the corresponding tab still exists and whether the session still matches, then updates the tab without unconditionally activating it.

AIClaw v3.7.11's release notes record 104 work interface checks, and v3.7.12 records a final total of 133 work interface checks.

The AIClaw reader stores the current view, diff layout, and scroll position separately per file, with source code, rendered Markdown, before-and-after snapshots, and each diff layout each having their own independent position key.

AIClaw's latest public version v3.7.14 still retains the docked reading area implementation.