v2.1.1

ai-memory 2.1.1

A patch release: correctness and cost fixes on top of 2.1.0. No new features, no
migrations, no config changes — safe to upgrade in place.

Fixed

• serve no longer re-archives the whole data dir on every start (#669). The
  OKF-conformance backup gate flagged the frontmatter-less monthly log-YYYY-MM.md
  event ledgers as pre-OKF, so a full tar.gz of the data dir was taken on every
  boot once a ledger existed. Ledgers are now excluded from that scan (the flip-side
  of 2.1.0's indexer fix). High-impact for long-running servers.
• Promptless internal sessions no longer flood the wiki (#662). A session is now
  synthesized into a sessions/<id>.md page only when it logged real work (a user
  prompt or a tool use). OpenCode's internal session.idle/branch-naming events —
  which emit only a stop — stop creating ephemeral no-op pages. Provider-agnostic;
  applied on both the router and the atomic store check.
• Wiki commits stop re-hashing the entire tree (#665). Since the #594 guard,
  every commit cleared the git index and re-read every page, so session-end cost
  grew with the wiki. Staging now uses libgit2's stat cache and re-hashes only on
  the rare tree-write failure; concurrent commits are serialized instead of dropping
  a snapshot.
• A capture-only .ai-memory.toml marker no longer resets scope to default
  (#668). A subdirectory marker added only to exclude paths from capture used to
  shadow an ancestor marker's workspace/project, filing pages under the wrong
  scope. Such a marker is now scope-transparent — fixed across all three front doors
  (POSIX/PowerShell scripts, the native binary, and the generated TypeScript
  integrations).
• Typed relations preserved in multi-page consolidation (#667). Batch updates
  now carry the closed causes/fixes/contradicts edges into frontmatter and the
  link index instead of silently discarding them.
• A leading UTF-8 BOM on a frontmatter-less page is dropped (#663), so the H1
  title is detected and the OKF conform pass doesn't push a stray marker into the
  body.

Changed

• The managed routing snippet notes that ai-memory is the cross-harness memory of
  record: durable project facts belong here, not duplicated in a harness's own local
  memory store that other agents can't see (#671).

See CHANGELOG.md
for the full list.

---

Checksums (SHA256)

b2425e64566e455473e067345054d006803e8090e828eb938b77ba8668518bd6  ai-memory-hooks.tar.gz
60cdc739c21f38b017c89f7fdc5708eb8d08fec715dfa62f364c23698094b074  ai-memory-install-hooks
72da124c2a9ab3843e44bef2d1b66a0f2313a4b557ad31578d99b2470c6be96c  ai-memory-linux-aarch64.tar.gz
5057d229e9bdcc488e284a11b9606b130b6ed6ccac79e541f42b6dfeb045ea73  ai-memory-linux-x86_64.tar.gz
1cc2acdbbd62cc7ecf6e1fe91515ea77786910b2c102f1fe8781aa6c0357eb64  ai-memory-macos-aarch64.tar.gz
3c2ca543abdf964c7fe4471e54824876d7327a04d0f222327ad6a8f010f78910  ai-memory-macos-x86_64.tar.gz
d65c989dbac7cceb6e8c587756db92dd3c145ec8743da591968992fb4e1babc3  ai-memory-windows-x86_64.zip
6a91c44ffa2e85d3b5a6ce26a4ccff0286b91d08d276d2bb4d47c346b036ee8b  ai-memory-wrapper.cmd
2d35c2f1fba28a1aee3ffeb58e3deaec772803f3dc6fd159de6ae0a47ba797ac  ai-memory-wrapper.ps1
127282baf003aec6a5e3a8c73c5186ff785c2a412c93e5538141ceb9b04909d9  ai-memory-wrapper

Install

# Arch Linux (AUR)
yay -S ai-memory-bin      # prebuilt Linux x86_64/aarch64 binary
yay -S ai-memory          # builds from source

# Docker
docker pull akitaonrails/ai-memory:2.1.1

# macOS aarch64/x86_64 (no toolchain): download the matching ai-memory-macos-<arch>.tar.gz below,
# extract it, and follow the bundled docs/macos.md.

# Windows x86_64 (no toolchain): download ai-memory-windows-x86_64.zip below,
# extract it, and follow the bundled docs/windows.md.

# From source
cargo install --locked --git https://github.com/akitaonrails/ai-memory --tag v2.1.1