Every release. Every fix. Every signed build.

OneMemory changes in public. Follow the intelligence layer, cloud rollout, desktop app, trust controls, and checksums here.

0.1.5, Windows (November 2026)

  • When OneMemory updates itself, its installer now ends OneMemory's own programs for you, including the helper your AI apps use. Until now an open AI app stopped such an update. The update can still be blocked when that helper runs with administrator rights, runs in another Windows session, or keeps starting again within about a second and a half. Running the installer yourself already ended those programs in 0.1.4. It does not close the AI apps. We tested this with the real signed installers and stand-in AI tools on Windows Server machines under an administrator account, not with real AI apps
  • If an AI app is open while OneMemory updates, OneMemory ends its connection to that app. Afterwards choose Restart AI tools in the OneMemory menu, or restart the app. For a terminal tool such as Claude Code, start a new session
  • After OneMemory updates itself, the new version has 10 minutes, counted from the start of the installation, to start and pass its health check. When you are signed in, part of that check asks the OneMemory servers about your account. Problems contacting the servers, server errors, rate limits and replies that cannot be used keep this part waiting. A refusal from the servers counts as an answer, and if the sign-in saved on this PC cannot be read, this part can pass without asking the servers. If it does not pass, OneMemory tries to put the previous version back by itself, and it does not delete the memories you had already saved. An app that blocks it, a Quit, or recovery files that cannot be checked can make it wait for you. While OneMemory checks and goes back, it does not save new memories
  • In three test rounds, each on two test machines, a test build of 0.1.5 that was made to fail its health check went back to 0.1.4 by itself. From the start of the update until 0.1.4 worked again it took between 21 and 25 minutes. For about 10 of those minutes the OneMemory tray and its local service were not running. Going back follows a five minute clock, so by design it takes about 20 to 25 minutes when nothing blocks it, and longer if something does. The real signed 0.1.4 and 0.1.5 installers also passed all four hosted update tests, including both rollback tests, with stand-in AI tools
  • Close AI apps that you started as administrator before you update. If OneMemory is not allowed to end its helper inside such an app, the installer refuses before it replaces any program file. An update that OneMemory started itself has by then already stopped OneMemory's local service. If a new version was already installed and has to be undone, going back can wait until you close that app. We have not tried this on a real PC
  • After an update that OneMemory installed, the new version's tray that took the update over can ask Windows for one notice, once it knows how the update ended and its icon is showing. When the update worked, it asks only if at least one AI app is set up, and the notice says that the new version is installed and that open AI apps need Restart AI tools. When the new version did not pass its check in time and its tray is still running, the notice says that OneMemory is going back to the previous version. There is no notice when the update was refused before it installed, when the new tray did not take over the update or stopped early, or when the update worked and no AI app is set up. Windows may not show the notice, the previous version that comes back shows none of its own, and we have not seen either notice on a real screen yet
  • When you choose Check for updates, the question that 0.1.5 asks before it installs a later version also says that open AI apps lose their OneMemory tools until you restart them. The question in 0.1.4, which you see before updating to 0.1.5, does not say this
  • OneMemory's background programs are built to end quietly when an unexpected error stops them, instead of leaving an 'Unhandled exception' window open. When such an error reaches the program's outer handler, the program tries to write a short record to OneMemory's log folder: the kind of error and the places in OneMemory's own code, nothing from your memories or files. A full drive, a full log folder or a blocked write can prevent the record. This is covered by development tests and has not been run in the installed app yet
  • When OneMemory's local service starts while OneMemory's local state file is busy, it now keeps retrying before it gives up. The pauses between its tries can add up to about 30 seconds, and the tries themselves and its other work take extra time. Once you are signed in, the capture watcher does the same. Version 0.1.4 gave up after about 2 seconds
  • OneMemory now ignores the Windows setting SSL_CERT_FILE when its file is missing or empty, when reading it fails before the text that starts a certificate is found, or when the whole file is read without finding that text. It ignores SSL_CERT_DIR when none of its folders exists. This avoids the Sign in errors that those ignored settings caused. Of a file larger than one megabyte only the first megabyte is read, and the setting is kept when nothing is found there. Whether a certificate is valid, what a certificate folder contains, and other network settings are not checked
  • Three changes are meant to reduce false 'not working' reports for a PC you just signed in. OneMemory's own checks of its AI tool connection no longer tell the hosted service that the local service is not answering, checks of hooks and connections that had failed before you signed in are reset and run again, and the hosted service waits 15 minutes after a new PC signs in before it reports a stopped helper for a PC whose helper has never reported. An AI app that really finds OneMemory not answering still counts
  • When the Stop check for Claude Code blocks the end of a turn, it now also writes its reason to the hook program's own error output, the stream that Claude Code's hook rules say it reads when a hook blocks. Tests that run the hook with real pipes show this. It has not been run in the installed app or in a live Claude Code session, so we have not yet seen Claude Code receive it
  • OneMemory's app now asks Windows for normal priority when it starts, if it was started at a lower one and no setting tells it to keep that priority. In 0.1.4, the helper that Windows Task Scheduler runs started OneMemory at the low background priority of a scheduled task, and the programs it started kept it. We checked the new behavior in tests with programs started at low priority and have not measured it in the installed app yet
  • The first sync of a large memory collection to a PC does less work: a new memory no longer makes OneMemory search the whole text index of the local copy. We have not measured the time this saves on a customer PC
  • Signed installer SHA-256: beb4aa822b255640468b2c4270e3b497958bbc01e24cba53ea8e1b8d867ddfdf

0.1.4, Windows (November 2026)

  • OneMemory keeps running after you sign in. Versions 0.1.1, 0.1.2 and 0.1.3 were missing a part they need, so their local service stops after sign-in and they cannot install an update by themselves. If you have one of them, download the 0.1.4 installer and run it over the old version. It replaces the program and leaves your OneMemory data folder as it is, so your memories and settings stay. If OneMemory asks you to sign in again, use the same email
  • You can run the installer while an older OneMemory is running. It first closes OneMemory's own programs, including the helper your AI apps use, and stops before copying any file if it cannot. Restart your AI apps afterwards. If the installer reports an error while copying, run it again
  • OneMemory starts by itself when you sign in to Windows, as long as the installer's 'Start OneMemory when Windows starts' option stays on. In our tests it was ready within 20 seconds of its start
  • Self-repair is more careful: after each repair step that changes something, the app checks again before it tries a bigger step, and fewer false alarms start a repair on a PC that works
  • A PC that had OneMemory before works again after you reinstall it and sign in again. For the first few minutes the account page may still show that PC as down
  • Uninstall stops the running app before it removes it. Close your AI apps first: while they are open they start OneMemory's helper again
  • The Stop check for Claude Code can read the session files that current Claude Code versions write; in 0.1.1 to 0.1.3 it could not. It only runs when OneMemory could not load memory for a prompt, and when it cannot tell it lets the turn finish. It has not been tried in a live Claude Code session with the installed app yet
  • Context builds made on the PC show on the Context-build runs page while Memory view is on
  • The hosted service masks common key, token and password formats in computer names and connected app names before it saves them, and refuses an API key name that contains one. Other formats are not detected, and names saved before this update are not changed
  • When you connect Gemini CLI, OneMemory adds its memory guidance to Gemini CLI's GEMINI.md file in a marked section, keeps it up to date and removes it on uninstall. Cursor and Claude Desktop have no such file: OneMemory sends them the guidance when they connect, and we have not confirmed yet that they pass it on to their AI
  • If you first set up OneMemory with 0.1.1 or 0.1.2 and have not changed your choices since: once 0.1.4 is installed and you are signed in, it shows a one-time window that offers what new installs now start with (saving your conversations, adding matching memories to your prompts, project memory packs). Nothing changes unless you press Apply
  • Signed installer SHA-256: f5326a212c57ec92bf4a5038439bec9119faaa4ec379dc5f120946dd77badea0

0.1.3, Windows (November 2026)

  • Everything on from the start for new installs: capture for supported AI clients, AI hooks, Codex capture, the Hermes brief, discovered tools and Project Memory Packs start selected; every box stays visible and a choice you have saved is never changed
  • Hosted dashboard, history and learning choices are on for accounts without a saved choice; turn any of them off on the account page
  • Trained neural recall: the shared re-scorer ranks hosted recall for accounts with neural recall enabled, and the app re-scores offline recall from its cache with the same model; the Learning panel tells hub ranking from offline scoring
  • API keys for scripts and clients: named keys with allowed actions, per-key scopes, a sensitivity ceiling and expiry (one year by default, two at most); rotation keeps the old key for ten minutes; revoke any time; REST at app.onememoryai.com with the X-API-Key header
  • Background intelligence for Free accounts within plan limits: living summaries, clustering, tiering, compaction and time-based invalidation run for every eligible account
  • Entity graph in the offline cache: entity rows reach your PC and offline recall pivots on them; 0.1.2 keeps working during the hosted update and 0.1.3 downloads the graph automatically
  • Credential facts: connected AI clients save what a credential is for and where it is kept, labelled sensitive with the credential tag, and leave the raw value out; recognizable secret values are replaced with placeholders before storage
  • AI tools and choices you turned off at setup can be turned on later: they are listed unticked in Connect AI tools
  • Events, Usage and Context-runs pages show counts and meters from your hosted account, in the Intelligence group of the dashboard menu
  • Memory map: a Dots shown slider sets how many memories the constellation draws (100 to 8,000) and remembers your choice
  • Customer manual at onememoryai.com/docs.html
  • Signed installer SHA-256: d82c8b2e88ba7ea7bb5b6338e48a5b7af7a393028ab17001c2ba7c8de20e8083

0.1.2, Windows (November 2026)

  • Pinned instructions: pin, unpin and list standing instructions from your AI tools or the command line; pins open every brief, followed by your project identity, living summary and recent work sessions
  • Held memories: keep or discard held candidates from the desktop dashboard, with the decision synced to every signed-in computer
  • Project Memory Packs: build a pack for a repository on your own PC after a separate opt-in; the hub never reads your files
  • Hosted account pages: memories, search and detail plus a history and audit view, off until you turn them on in your account settings
  • Desktop memory detail: writer, source, timestamps, confidence, origin, scope and live audit history
  • System Health, Connections and Systems panels, an activity rail for every connected AI tool, cloud analysis and bring-your-own-key settings, clearer tray states for offline, delayed and sign-in-required
  • Codex capture (opt-in), exact read-only tool approvals for Codex and Claude Code, a chat-only brief by default outside projects
  • Hermes briefs (opt-in), automatic detection of newly installed AI tools with one Apply click, crash reports you review and send yourself
  • Computers on this account with last seen and feed lag; signed update checks at startup and every six hours; on-device semantic recall from the bundled model
  • Hosted MCP catalog grows from 14 to 26 tools; worklog entries reach every PC
  • Learning data per account and a learned re-scorer for accounts stay off until enabled
  • Signed installer SHA-256: e1de4349b3a645451be2b7edff37216c3a68e88e2dabe8de66d0d03ede5fde22

Neural recall, private beta (September 2026)

  • First trained neural network inside OneMemory recall
  • Reranks the strongest memory candidates after access and sensitivity filters run
  • Nightly training with champion-and-challenger promotion gates for accuracy, safety, and speed
  • Learning panel shows the active model, training history, benchmark trend, and memories moved
  • Constellation pulses when neural recall lifts or lowers a memory

0.1.0, private beta (July 2026)

  • First packaged Windows release: single tray app bundling the memory server, observer, and MCP bridge
  • First-run wizard with observer consent and one-click wiring for Claude Code, Claude Desktop, Cursor, and Codex
  • Local embeddings included (bge-small ONNX); recall works fully offline
  • Beta access is free for every account
  • Zero-touch policy engine, scoped vaults, hash-chained audit log, secret redaction
  • Admin dashboard opens on a live 3D memory constellation

Checksums appear here with every public signed build.