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