We upgraded every GBrain workspace to OpenClaw 2026.9.6 and GBrain 0.59.3. OpenClaw is the open-source program that runs the AI in each workspace, and GBrain is the open-source memory it reads and writes. A workspace is where a person or a team keeps that memory and talks to the AI.
The versions
| Part | Before | Now |
|---|---|---|
| OpenClaw | 2026.8.2 | 2026.9.6 |
| GBrain | 0.48.0.0 | 0.59.3.0 |
| Node.js | 22 | 24 |
| Postgres | 17.11 | 17.11 |
| pgvector | 0.8.0 | 0.8.0 |
Node.js runs OpenClaw, and Postgres with pgvector is the database the memory is stored and searched in.
What you might notice
Search catches up. After the upgrade, GBrain updates every page in the memory once, and search can miss a page until GBrain has updated it. Most workspaces finished in minutes. The largest take several hours.
Overwriting a page checks its revision. A revision is the page’s version number. Code that updates an existing page through GBrain’s MCP server (the standard way AI apps connect to GBrain) or its command line now has to pass the page’s current revision, or force. Creating a page works as before.
Six more memory tools. A tool is one action an AI can take in the memory. GBrain’s MCP server went from 27 tools to 33, adding tools for skills (saved instructions an AI can follow) and for receipts that confirm what was written.
The nightly tidy-up of memory moved. It used to start at 03:00 UTC for every workspace at once. Each workspace now starts at its own time between 03:00 and 07:00 UTC.
ZeroEntropy is gone. GBrain 0.56.2 removed ZeroEntropy, one of the services that turned memory into the numbers search matches against (embeddings). Memory is embedded with OpenAI’s models.
Security fixes
- OpenClaw: reading its settings no longer shows passwords or keys, web requests that skip its network filter are checked for where they really go, the page that reports its internal numbers now needs a sign-in, and a message can no longer pass as someone else’s by claiming so in its text.
- GBrain: stricter rules for who can reach the memory, the owner has to agree before another app is given access to it, checks on the web pages GBrain fetches, and passwords and keys blanked out of what it shows.
What you need to do
Nothing, unless you’ve written code that overwrites memory pages. It has to pass the page’s current revision, or force.
The full upstream notes are in the OpenClaw releases and the GBrain changelog.