keep-v0.1.0-alpha.2

Keep 0.1.0-alpha.2 release notes

Keep provides shared local memory for AI agents through stdio or protected HTTP.
This alpha provides Linux x64 with glibc, Windows x64, and macOS Apple Silicon archives.

Windows now includes the MSVC runtime in the executable. No separate Visual C++ Redistributable installation is required for alpha.2.
Model downloads no longer fail intermittently when a server closes its connection after each file.
The document API, license, and dependency notices remain unchanged.

Tested systems

Condition	Linux x64	Windows x64	macOS arm64
OS	Ubuntu 24.04.5 LTS; kernel 6.8.0-142-generic	Windows 11, build 10.0.26200	macOS 26.5.1
Visible logical CPUs	16	32	8
Physical memory bytes	16,765,132,800	66,217,689,088	17,179,869,184
Model, cache recovery, and backup checks	Passed	Passed	Passed

These are tested hosts, not minimum system requirements. No clean-machine installation result is claimed.

Model and limits

Default search is lexical and needs no model. Add --semantic to enable hybrid search with a local model.
The archives contain no model weights; the first enabled start can download about 86 MiB.
The pinned model is Snowflake/snowflake-arctic-embed-xs, revision d8c86521100d3556476a063fc2342036d45c106f.
All three platforms passed model checksum checks, corrupt-cache recovery, hybrid search, and lexical fallback after model failure.

Hybrid search permits at most 512 documents, 4,096 chunks, and 8,388,608 searchable text bytes across the store.
Narrow filters do not bypass these limits. Use lexical search when a model is unavailable or a hybrid limit is exceeded.
The measured dataset contains 512 documents, 4,096 chunks, and 6,814,994 searchable text bytes.
It does not exercise the complete 8 MiB text limit. Lexical search remained available after a 513th document exceeded the document limit.

Observed costs

Measurement	Linux x64	Windows x64	macOS arm64
Initial download, verification, and model load	2.587 s	6.625 s	3.295 s
Model load with verified cache in a fresh process	97.475 ms	62.000 ms	60.829 ms
Index wall time	842.655 s	681.516 s	615.514 s
Index CPU time	1,090.380 s	3,571.594 s	1,427.570 s
Sampled peak resident memory	208,609,280 bytes	219,582,464 bytes	227,229,696 bytes
One warm hybrid query	321.129 ms	281.000 ms	350.763 ms
Maximum sample gap during initial download and load	31.123 ms	3,546.000 ms	462.880 ms
Maximum sample gap during cached-process measurements	33.148 ms	63.000 ms	403.011 ms

The hosts are shared, with no exclusive CPU allocation. Linux has a two-CPU quota and a 4 GiB memory limit.
Inherited Linux limits can be stricter. Windows job-object restrictions were not queried.

Cached measurements use a fresh process, verified model files, and the same dataset. The OS file cache stays warm.
Model and index times use observed phase transitions. Index CPU time includes protocol work; resident memory is a sampled peak.
The warm query cost covers one request after readiness.

The requested sample interval is 10 ms. Actual gaps limit precision.
The Windows initial-load observation spans 6.625 seconds, with a 3.546-second maximum sample gap; it is coarse.
Windows and macOS cached model-load intervals are shorter than their maximum sample gaps and are also coarse.
These results establish no general speed benefit, memory maximum, or comparison with another product.

Fresh-agent tasks

Fresh agents completed all five tasks on each native archive.
The tasks covered exact queries, conditional edits, history restoration, archive access, and deletion.
Linux and Windows used 19 MCP calls; macOS used 20.
Each trial had four requested mutations and one expected not_found response. No unexpected MCP errors occurred.
The evaluator model was GPT-6.1 Sol with medium reasoning. These trials provide exploratory evidence without a product comparison.

Integrity and recovery

This alpha uses checksums-only integrity. The archives are unsigned.
Download the archive and SHA256SUMS from the same prerelease. Compare the archive's SHA-256 before extraction.
Use the public README for installation and client setup.
Stop Keep before a backup or restore. A restored backup loses later writes.
Uninstall removes only the executable; the personal store and backups remain on disk.