Raven 0.2.2 (2026-09-25)

Raven 0.2.2 is a patch release with one thing worth reading before you upgrade: memory runs on native Windows now. No command, flag or config key is removed or renamed, and no configured default changes. The memory plugin's EverOS pin moves from 1.2.3 to 1.4.1, which runs on Windows without WSL, so the platform gate that made memory unavailable there is gone. Two guards found while verifying against a copy of a real 1.2.x store come with it: an embedding model narrower than the memory index is refused rather than left to answer 500 on every store and search, and an upgrade no longer leaves the old server answering on the port (#791).

Highlights

Memory on native Windows

• The platform gate is gone. everos_platform_note and its five call sites, the UNSUPPORTED service state, the import scan's refusal and the wizard's WSL notice are removed, and Raven looks for everos.exe on Windows. Spawning, probing and reusing the server were already portable; identifying and stopping one was not. The command line now comes from WMI through PowerShell, the listening port from the TCP table, walking the launcher's descendants to the interpreter that actually holds the socket.

• The server is spawned in a process group of its own, so a Ctrl-C at the gateway's console does not take it down with it, and stopped with Ctrl-Break, which uvicorn takes as a shutdown; one that ignores it for ten seconds is terminated as before. Because Windows cannot replace a running executable, raven upgrade stops whatever still runs from under the tool environment before it installs -- the memory server outlives the gateway by design, and without that stop uv failed on Scripts\everos.exe.

Two guards for the memory store

• An embedding model narrower than the 1024-wide memory index is refused where it is pinned, and withheld from the server it would otherwise have started. A 768-dimension model saved from the settings page had left every memory store and search answering 500 about a mismatched width, with nothing on the page saying why. EverOS then runs keyword recall and keeps storing, and the notice names the model and its width. A probe that cannot reach the provider is not a verdict: the pin is written and a warning logged.

• A running EverOS whose version no longer matches the installed one is replaced rather than reused, through the same precheck, stop and spawn chain a rotated credential takes. An upgrade used to leave the old server serving until something unrelated restarted it. A root you manage yourself is never touched. And a gateway that finds nothing listening and no lock held starts the server again, at most once every thirty seconds, so a server that goes away no longer leaves that gateway without memory until you restart it by hand.

Recall and the memory page

• Recall on the Cases and Know-how tracks searches by vector when no reranker is configured, instead of asking for an LLM rerank that the four-second recall budget can never wait out.

• The memory page reads the /api/v2 routes, asks /health before a search the way the chat adapter does, and shows the server's own sentence on a refusal. A recalled profile is drawn as lines rather than a namespace(...) repr, a tool-call-only row stores empty content rather than the string "None", an empty query asks nothing, and top_k stays within 1..100.

• The first-run wizard accepts an embedding model wider than 1024 (EverOS keeps the first 1024, as the settings page already allowed) and re-prompts on a refusal instead of showing a traceback.

Under the wire

• Every request body the plugin and the memory page send is validated against EverOS 1.4.1's own request models in the suite, so a schema move on the next upgrade fails a test rather than a gateway log. The upgrade is recorded in docs/memory-plugin-architecture.md section 7.4.

Install

New install on Linux, macOS, or WSL2:

curl -fsSL https://raven.evermind.ai/install.sh | bash

New install on native Windows, in PowerShell:

irm https://raven.evermind.ai/install.ps1 | iex

Windows PowerShell 5.1 (the version built into Windows) rejects that URL with
Permanent Redirect; use the direct one instead:

irm https://raw.githubusercontent.com/EverMind-AI/Raven/refs/heads/main/install.ps1 | iex

The installer puts uv, Node.js 22, Raven and its plugins in place, downloads the
browser runtime, installs or offers LibreOffice, and then finishes by opening
Raven in your browser. First-run setup happens on that page. The installer holds
the terminal while the page is up; press Ctrl-C to stop it, then start Raven
again with:

raven web

That keeps Raven running in the background and opens the page; raven web --stop
stops it. Prefer the terminal? raven runs the same first-run setup and opens
the TUI, and raven onboard stays the explicit way to reconfigure later. Set
RAVEN_MINIMAL=1 to skip the browser and LibreOffice downloads, or
RAVEN_NO_LAUNCH=1 to have the installer return without opening the page.

Upgrade

Already running Raven? Upgrade in place -- configuration, sessions, and memory
are preserved. Stop the page first, then upgrade:

raven web --stop
raven upgrade

On Linux and macOS raven upgrade runs the install in the foreground and
returns when it is done. On native Windows it hands the install to a separate
helper and returns at once; wait for the helper's completion message. Then
start Raven again:

raven web

raven upgrade installs the latest stable release together with the plugin
wheels it ships. It never picks up a pre-release unless this install has joined
the beta channel (a ~/.raven/beta.json that only the beta installer writes).
raven upgrade --check reports whether a newer release exists without
installing it. Editable source checkouts are never overwritten: raven upgrade
reports the checkout path and how far it is ahead of or behind origin/main,
and the remedy is git pull && ./install.sh in the checkout. Rerunning the
one-line installer also upgrades, and ends on the running page.

Release Status

• Version: 0.2.2
• Tag: v0.2.2
• Stability: public preview patch
• Assets: the raven wheel and source distribution, the three plugin wheels
  (everos_memory, design_engine, ppt_engine), the locked constraints file
  raven-constraints.txt, and the plugin list raven-plugins.txt

Notes

• Raven is still pre-1.0; CLI surfaces, plugin contracts, and runtime internals may continue to evolve.
• PyPI publishing is not enabled yet; the supported public install path uses the GitHub Release wheel asset.