1. Download free
Request your free access with an email address, then run OneMemory-Setup.exe. It installs for your Windows user and starts the tray app. No admin prompt appears.
Create free access. Install OneMemory. Connect your AIs. Save one memory and recall it from another tool.
Request your free access with an email address, then run OneMemory-Setup.exe. It installs for your Windows user and starts the tray app. No admin prompt appears.
The first-run setup asks plainly before enabling session observation. Capture is off until you turn it on. You can change the choice later from the tray app.
Start a new session and ask, "What do you remember about me?" Claude Code should call the onememory MCP tools. You can also inspect /mcp for the server entry.
Restart Claude Desktop after setup. The tools menu should list onememory.
Start a new session. Codex reads the OneMemory MCP entry from its configuration automatically after the installer wires it.
Add onememory as an MCP server in the client settings, then restart the client.
Tell a connected AI: "Remember that staging deploys run from the release branch."
OneMemory turns the statement into a source-backed claim, redacts any secret material, applies policy, and activates the memory if it passes. No approval chore is required.
Open another connected AI and ask how staging deploys work. It should recall the memory, its scope, and its evidence.
Open the dashboard to see the memory in the constellation. Inspect which AI wrote it, which computer observed it, when it arrived, and what source supports it.
If cloud sync is enabled for your account, open OneMemory on another computer and check the sync status. Portable memory should appear with its origin computer intact. Host-local facts should remain identified as computer-specific.
%LOCALAPPDATA%\OneMemory\ onememory.sqlite3 desktop working memory config.env local settings and client key logs\ service, observer, and tray logs backups\ desktop backups
The desktop working store supports fast and offline recall. Cloud sync is a separate lane and follows the sync policy shown in the app.
Quit OneMemory from the tray, then start it again from the Start menu. Check logs\server.err.log if it stays offline.
Restart that AI client. MCP servers load when the client starts. Run the connection step again from OneMemory settings if needed.
Set ONEMEMORY_PORT in config.env, restart OneMemory, then reconnect the clients.
Hosted consumer sync is rolling out through the beta. Confirm that the account is enabled and the computer is online. Desktop recall continues while sync is unavailable.
Use Export in the dashboard. Full export is included.
Email hello@onememoryai.com. Include the relevant log files for a crash. Review them before sending and remove anything you do not want to share.