Docs

Windows

Installing, updating and rolling back on Windows, where data lives, and how embeddings run on the CPU.

The Windows app covers the same ground as the Mac: capture, cloud, local and hybrid storage, search, replay, the CLI and MCP stdio, and running in the background. It doesn't need a Mac.

Install and update

Windows ships as a self-contained bundle. Each version installs into its own folder, and the installer checks every file against SHA-256 before switching to it, so a failed update leaves the previous version in place. Rolling back means returning to the previous version's folder.

Installing or uninstalling never removes your data. The database, settings and stored credentials stay.

Hooks and background running

The Claude Code, Codex, Devin CLI and Grok hooks point to a fixed shim that calls the console CLI, so updates don't break them. The app starts with Windows through your user Run key, and a periodic sweep picks up anything a hook missed.

%LOCALAPPDATA%\Agent Memory\bin\agent-memory-session-end-hook.cmd

Where data lives

What	Where
Database	`%LOCALAPPDATA%\Agent Memory\local\db.sqlite`
Embedding model	`%LOCALAPPDATA%\Agent Memory\models\bge-m3`
Credentials	Windows Credential Manager

Embeddings

Windows runs BGE-M3 with onnxruntime on the CPU and produces vectors in the same space as the Mac. The bundle includes sqlite-vec but not the model. Without the model, search falls back to words, as it does on the Mac.

Windows signs in with OAuth 2.1 and PKCE through your browser and keeps tokens in the Windows Credential Manager.