AIClaw
A desktop collaboration tool for developers working with AI agents. It supports file preview and change review, uses an Electron architecture, and enables secure local file reading through session isolation.
Timeline (last 90 days)
AIClaw's MemoryView component distinguishes "file does not exist" from "read failure": a missing memory file can be created by editing, whereas a read error is shown as an error rather than as empty memory.
AIClaw's tagged release workflow has completed successfully, including test, packaging, and release jobs, and its workflow definition runs a desktop smoke check under a Linux virtual display.
AIClaw's public filesystem tests cover missing files, read errors, text preservation, UTF-8 capacity, conflicts, empty-file saving, and protected paths; the symbolic link test is explicitly skipped on Windows.
Saving memory on AIClaw's Memory page only updates the on-disk file and does not directly rebuild the system prompt of the current conversation; memory is loaded when a session is opened or resumed.
Before writing memory, the AIClaw host rejects memory files in the form of symbolic links, and rejects null characters and content over the limit.
AIClaw's memory write flow is: first write a temporary file in a temporary directory next to the target, check the snapshot again, then rename the new file into place, and finally clean up the temporary directory.
AIClaw memory saving uses optimistic concurrency control: the editor carries a snapshot of the content it initially read, the host compares the current content before writing, and if they differ the save fails with a prompt to refresh, while the UI retains the draft.
AIClaw's Memory edit write paths are resolved by the main process: the global path is resolved from the app configuration, and the workspace path is formed by resolving the working directory from the owning non-archived session and then appending the fixed memory path; the renderer process does not choose arbitrary target file names.
The per-document save limit for AIClaw memory files is 32 KiB (counted in UTF-8 bytes), consistent with the desktop kernel's memory loading limit.
In AIClaw's memory editor, the entry boundary rule is: a line starting with a hyphen or asterisk begins a new entry, and subsequent lines belong to that entry; this is text grouping rather than a full Markdown document model.
40 more timeline events
All Facts (20)
The per-document save limit for AIClaw memory files is 32 KiB (counted in UTF-8 bytes), consistent with the desktop kernel's memory loading limit.
50%UnverifiedSaving memory on AIClaw's Memory page only updates the on-disk file and does not directly rebuild the system prompt of the current conversation; memory is loaded when a session is opened or resumed.
50%UnverifiedAIClaw's Memory edit write paths are resolved by the main process: the global path is resolved from the app configuration, and the workspace path is formed by resolving the working directory from the owning non-archived session and then appending the fixed memory path; the renderer process does not choose arbitrary target file names.
50%UnverifiedAIClaw memory saving uses optimistic concurrency control: the editor carries a snapshot of the content it initially read, the host compares the current content before writing, and if they differ the save fails with a prompt to refresh, while the UI retains the draft.
50%UnverifiedBefore writing memory, the AIClaw host rejects memory files in the form of symbolic links, and rejects null characters and content over the limit.
50%UnverifiedAIClaw's memory write flow is: first write a temporary file in a temporary directory next to the target, check the snapshot again, then rename the new file into place, and finally clean up the temporary directory.
50%UnverifiedAIClaw's public filesystem tests cover missing files, read errors, text preservation, UTF-8 capacity, conflicts, empty-file saving, and protected paths; the symbolic link test is explicitly skipped on Windows.
50%UnverifiedAIClaw's MemoryView component distinguishes "file does not exist" from "read failure": a missing memory file can be created by editing, whereas a read error is shown as an error rather than as empty memory.
50%UnverifiedAIClaw's Memory page displays two types of memory: global memory, usually located at ~/.aiclaw/memory.md, and workspace memory, located at .aiclaw/memory.md under the working directory.
50%UnverifiedIn AIClaw's memory editor, the entry boundary rule is: a line starting with a hyphen or asterisk begins a new entry, and subsequent lines belong to that entry; this is text grouping rather than a full Markdown document model.
50%UnverifiedFor 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.
50%UnverifiedAIClaw'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.
50%UnverifiedAIClaw's updater refuses to install from development mode; a release with only a ZIP falls back to the previous "download and open folder" behavior.
50%UnverifiedThe 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.
50%UnverifiedAIClaw'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.
50%UnverifiedAIClaw 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.
50%UnverifiedWhen a checksum entry is missing or the digest does not match, AIClaw does not open the installer, and the application keeps running.
50%UnverifiedAIClaw'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.
50%UnverifiedAIClaw's SHA256SUMS.txt format is "digest + two spaces + filename" per line, originating from the GNU coreutils sha256sum tool.
50%UnverifiedAIClaw's current installer has no Authenticode signature, so Windows may show an unknown publisher warning.
50%