We upgraded every GBrain workspace to OpenClaw 2026.9.6 and GBrain 0.59.3.
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 |
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. Code that updates an existing page through GBrain’s MCP server or command line now has to pass the page’s current revision, or force. Creating a page works as before.
Six more memory tools. GBrain’s MCP server went from 27 tools to 33, adding tools for skills and write receipts.
Nightly memory consolidation 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 the ZeroEntropy embedding provider. Memory is embedded with OpenAI’s models.
Security fixes
- OpenClaw: reading the configuration no longer shows secrets, requests that bypass the proxy have their DNS checked, the metrics endpoint requires authorization, and a message can no longer pass as someone else’s by claiming so in its text.
- GBrain: stricter access rules for memory, the owner’s consent before an OAuth grant, checks on outbound fetches, and secret redaction.
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.