Skip to content

Garry's Opinionated OpenClaw/Hermes Agent Brain

TypeScript

v0.60.731.0 release (#9470)

Garry Tan1d30ed422e2a
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index 777b8874e2..d741e25221 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain",
- "version": "0.60.730.0",
+ "version": "0.60.731.0",
"description": "Personal knowledge brain for your coding agent — hybrid search, synthesis, graph traversal, and durable cross-session memory over Postgres/PGLite with pgvector, plus a curated brain-first skill set.",
"author": {
"name": "Garry Tan",
diff --git a/.codex-plugin/plugin.json b/.codex-plugin/plugin.json
index 28c4b38e9e..3c2eec59b5 100644
--- a/.codex-plugin/plugin.json
+++ b/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain",
- "version": "0.60.730.0",
+ "version": "0.60.731.0",
"description": "Personal knowledge brain for your coding agent — hybrid search, synthesis, graph traversal, and durable cross-session memory over Postgres/PGLite with pgvector, plus a curated brain-first skill set.",
"author": {
"name": "Garry Tan",
diff --git a/BOOTSTRAP_FOR_AGENTS.md b/BOOTSTRAP_FOR_AGENTS.md
index c0dad19153..21444a6d65 100644
--- a/BOOTSTRAP_FOR_AGENTS.md
+++ b/BOOTSTRAP_FOR_AGENTS.md
@@ -1,4 +1,4 @@
-<!-- gbrain-runbook-stamp: 0.60.730.0 -->
+<!-- gbrain-runbook-stamp: 0.60.731.0 -->
<!-- This stamp must equal the VERSION file at every release; CI enforces it
(scripts/check-bootstrap-tag.sh). `gbrain bootstrap status` compares it to
the installed binary and warns on skew. -->
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 4b9ef09b9d..f634fcd99d 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,47 @@ credits are retained; no result has been reassigned to another provider. Origina
identifiers and attribution are available in the pre-removal Git revision
`6040075c6cb95be5881cc2e1b76ef7d71f4e5d29` (retained on 2026-09-23).
+## [0.60.731.0] - 2026-11-16
+
+**docs/STABILITY.md now says what stays the same on the stable channel, and how much warning you get before something changes.**
+
+### Added
+- A "What stays the same on stable" section in docs/STABILITY.md. It covers command names and their documented flags, MCP tools and their parameters, documented config keys, the page and frontmatter format, exit codes and the top-level `--json` fields of documented commands, and upgrades from any stable release of the last six months. A removal or rename is announced in a stable release first, keeps working with a warning, and is removed no sooner than 14 days and two stable releases later. Security and data-loss fixes are the one exception. The section also lists what the promise does not cover, including very large brains during an upgrade until #9192 is fixed.
+- `deprecations.d/README.md`, which says how a planned removal is recorded and announced before it happens.
+- The README's Stability section points to the new promise.
+
+**Stable now waits for a green upgrade test from every recent stable release.**
+
+### Changed
+- The daily stable check promotes a release only after the upgrade matrix ran green on that release's exact tag and tree. With no run yet it starts one; a red run holds stable with a warning and is not started again by the schedule.
+- The upgrade matrix's full run also upgrades from the stable releases users may still be on, which are the last 8 stable releases plus the newest one of each older month, back 6 months. A test run from before this change no longer counts.
+- While the upgrade matrix's own break issue is open, stable holds. Only a security or data-loss fix that fails on no from-version the issue doesn't name may pass it.
+- `promote-stable.yml` takes an optional `matrix_run_url`, checks it the same way and records it as `matrix_run` in `stable.json` and the stable tag. A maintainer can still promote without one, recorded as `matrix_run: null`.
+
+**Doctor, init, call import and gbrain serve report and record the right thing in seven small cases.**
+
+### Fixed
+- `gbrain doctor`'s grant check is ok when the only operations a grant misses are ones the owner adds by name, and its message names them with the command that adds them.
+- `gbrain import --calls` finds a call already imported from any folder above the one you import, and reports a call whose page is still being written as pending instead of writing a second copy; with `--accept-pending` it still exits 10 when that write waits on a stale owner host.
+- A folder whose `.git` is an empty file is no longer taken as a git checkout.
+- Release notes drop a trailing internal issue code, like `(ABC-12)`, from each line of the change list.
+- `gbrain init --force --embedding-model <model>` records the new model and width in the database as well as the config file, so the two agree (#9451).
+- `gbrain serve` names upgrade migrations that haven't run, once at startup on stderr, and `gbrain doctor` reports them too, also on a brain an older release last opened whose local upgrade ledger is empty.
+
+### For contributors
+- The key-files page `google-and-loops.md` was at its 60,000-byte cap, so its harness and MCP entries moved unchanged to `google-and-loops-more.md`; the Google source entry now says what an unmanaged `--dry-run` returns.
+
+Reported by @Loprz (#9451).
+
+**Stable moves within a day only for security, data-loss and stable-regression fixes; everything else waits for the weekly move.**
+
+### Changed
+- An important fix, the kind that moves the stable channel early, is now only a security fix, a data-loss fix or a fix for a regression in a release that is on stable. A fix that unblocks one setup, or a regression only alpha releases have, rides the weekly move unless a maintainer promotes by hand. `gbrain upgrade --help`, docs/STABILITY.md, docs/RELEASING.md ("Daily stable check") and changelog.d/README.md say so.
+- `scripts/build-behavior-changes.ts` (in `check:regen-all`) refuses a changelog fragment whose `important:` class is anything but `security`, `regression` or `data-loss`, naming the three and docs/RELEASING.md#daily-stable-check, the same way it refuses a `bump:` other than `patch`. A `# comment` after a front-matter value is no longer read as part of it.
+- Tests: `test/scripts/build-behavior-changes.test.ts` covers the refused and accepted `important:` values.
+
+<!-- behavior-change: stable_important_three_classes_gst2818 -->
+
## [0.60.730.0] - 2026-11-16
**A dry run of a Google or GitHub source no longer writes pages (#9449).**
diff --git a/VERSION b/VERSION
index 2794823352..941f73d2cb 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-0.60.730.0
+0.60.731.0
diff --git a/changelog.d/capy-stable-promise.md b/changelog.d/capy-stable-promise.md
deleted file mode 100644
index 49ab24a2fb..0000000000
--- a/changelog.d/capy-stable-promise.md
+++ /dev/null
@@ -1,6 +0,0 @@
-**docs/STABILITY.md now says what stays the same on the stable channel, and how much warning you get before something changes.**
-
-### Added
-- A "What stays the same on stable" section in docs/STABILITY.md. It covers command names and their documented flags, MCP tools and their parameters, documented config keys, the page and frontmatter format, exit codes and the top-level `--json` fields of documented commands, and upgrades from any stable release of the last six months. A removal or rename is announced in a stable release first, keeps working with a warning, and is removed no sooner than 14 days and two stable releases later. Security and data-loss fixes are the one exception. The section also lists what the promise does not cover, including very large brains during an upgrade until #9192 is fixed.
-- `deprecations.d/README.md`, which says how a planned removal is recorded and announced before it happens.
-- The README's Stability section points to the new promise.
diff --git a/changelog.d/capy-stable-waits-for-a.md b/changelog.d/capy-stable-waits-for-a.md
deleted file mode 100644
index c63d936477..0000000000
--- a/changelog.d/capy-stable-waits-for-a.md
+++ /dev/null
@@ -1,7 +0,0 @@
-**Stable now waits for a green upgrade test from every recent stable release.**
-
-### Changed
-- The daily stable check promotes a release only after the upgrade matrix ran green on that release's exact tag and tree. With no run yet it starts one; a red run holds stable with a warning and is not started again by the schedule.
-- The upgrade matrix's full run also upgrades from the stable releases users may still be on, which are the last 8 stable releases plus the newest one of each older month, back 6 months. A test run from before this change no longer counts.
-- While the upgrade matrix's own break issue is open, stable holds. Only a security or data-loss fix that fails on no from-version the issue doesn't name may pass it.
-- `promote-stable.yml` takes an optional `matrix_run_url`, checks it the same way and records it as `matrix_run` in `stable.json` and the stable tag. A maintainer can still promote without one, recorded as `matrix_run: null`.
diff --git a/changelog.d/fix-small-fix-wave-3.md b/changelog.d/fix-small-fix-wave-3.md
deleted file mode 100644
index 86ea1627b3..0000000000
--- a/changelog.d/fix-small-fix-wave-3.md
+++ /dev/null
@@ -1,14 +0,0 @@
-**Doctor, init, call import and gbrain serve report and record the right thing in seven small cases.**
-
-### Fixed
-- `gbrain doctor`'s grant check is ok when the only operations a grant misses are ones the owner adds by name, and its message names them with the command that adds them.
-- `gbrain import --calls` finds a call already imported from any folder above the one you import, and reports a call whose page is still being written as pending instead of writing a second copy; with `--accept-pending` it still exits 10 when that write waits on a stale owner host.
-- A folder whose `.git` is an empty file is no longer taken as a git checkout.
-- Release notes drop a trailing internal issue code, like `(ABC-12)`, from each line of the change list.
-- `gbrain init --force --embedding-model <model>` records the new model and width in the database as well as the config file, so the two agree (#9451).
-- `gbrain serve` names upgrade migrations that haven't run, once at startup on stderr, and `gbrain doctor` reports them too, also on a brain an older release last opened whose local upgrade ledger is empty.
-
-### For contributors
-- The key-files page `google-and-loops.md` was at its 60,000-byte cap, so its harness and MCP entries moved unchanged to `google-and-loops-more.md`; the Google source entry now says what an unmanaged `--dry-run` returns.
-
-Reported by @Loprz (#9451).
diff --git a/changelog.d/stable-important-three-classes.md b/changelog.d/stable-important-three-classes.md
deleted file mode 100644
index 25f1e16e6a..0000000000
--- a/changelog.d/stable-important-three-classes.md
+++ /dev/null
@@ -1,8 +0,0 @@
-**Stable moves within a day only for security, data-loss and stable-regression fixes; everything else waits for the weekly move.**
-
-### Changed
-- An important fix, the kind that moves the stable channel early, is now only a security fix, a data-loss fix or a fix for a regression in a release that is on stable. A fix that unblocks one setup, or a regression only alpha releases have, rides the weekly move unless a maintainer promotes by hand. `gbrain upgrade --help`, docs/STABILITY.md, docs/RELEASING.md ("Daily stable check") and changelog.d/README.md say so.
-- `scripts/build-behavior-changes.ts` (in `check:regen-all`) refuses a changelog fragment whose `important:` class is anything but `security`, `regression` or `data-loss`, naming the three and docs/RELEASING.md#daily-stable-check, the same way it refuses a `bump:` other than `patch`. A `# comment` after a front-matter value is no longer read as part of it.
-- Tests: `test/scripts/build-behavior-changes.test.ts` covers the refused and accepted `important:` values.
-
-<!-- behavior-change: stable_important_three_classes_gst2818 -->
diff --git a/openclaw.plugin.json b/openclaw.plugin.json
index 5acb9ef788..271d947d49 100644
--- a/openclaw.plugin.json
+++ b/openclaw.plugin.json
@@ -1,7 +1,7 @@
{
"id": "gbrain-context-engine",
"name": "gbrain",
- "version": "0.60.730.0",
+ "version": "0.60.731.0",
"description": "Personal knowledge brain with Postgres + pgvector hybrid search",
"family": "bundle-plugin",
"kind": "context-engine",
diff --git a/package.json b/package.json
index 6ccea9005c..f3489f4a34 100644
--- a/package.json
+++ b/package.json
@@ -260,7 +260,7 @@
"bun": ">=1.4.4"
},
"license": "MIT",
- "version": "0.60.730.0",
+ "version": "0.60.731.0",
"overrides": {
"@aws-sdk/util-format-url": "3.972.9",
"@ai-sdk/provider-utils": "4.0.56",
diff --git a/plugin-variants/gbrain-coding/.claude-plugin/plugin.json b/plugin-variants/gbrain-coding/.claude-plugin/plugin.json
index 7caf115640..8166f96110 100644
--- a/plugin-variants/gbrain-coding/.claude-plugin/plugin.json
+++ b/plugin-variants/gbrain-coding/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain-coding",
- "version": "0.60.730.0",
+ "version": "0.60.731.0",
"description": "Brain-first coding agent working inside a repo: retrieval, routing, ingest discipline, correction hygiene. Default persona for the claude-code harness bridge; also published as the gbrain-coding marketplace variant. (persona variant of the gbrain plugin — 21 skills)",
"author": {
"name": "Garry Tan",
diff --git a/plugin-variants/gbrain-coding/.codex-plugin/plugin.json b/plugin-variants/gbrain-coding/.codex-plugin/plugin.json
index 75158ac31a..8b9e836cbf 100644
--- a/plugin-variants/gbrain-coding/.codex-plugin/plugin.json
+++ b/plugin-variants/gbrain-coding/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain-coding",
- "version": "0.60.730.0",
+ "version": "0.60.731.0",
"description": "Brain-first coding agent working inside a repo: retrieval, routing, ingest discipline, correction hygiene. Default persona for the claude-code harness bridge; also published as the gbrain-coding marketplace variant. (persona variant of the gbrain plugin — 21 skills)",
"author": {
"name": "Garry Tan",
diff --git a/plugin-variants/gbrain-coding/README.md b/plugin-variants/gbrain-coding/README.md
index e0c9c79537..234c9628d5 100644
--- a/plugin-variants/gbrain-coding/README.md
+++ b/plugin-variants/gbrain-coding/README.md
@@ -1,4 +1,4 @@
-<!-- gbrain-plugin-tree-stamp: 0.60.730.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.731.0 -->
# gbrain-coding (generated persona variant — do not hand-edit)
Brain-first coding agent working inside a repo: retrieval, routing, ingest discipline, correction hygiene. Default persona for the claude-code harness bridge; also published as the gbrain-coding marketplace variant.
diff --git a/plugin-variants/gbrain-daily/.claude-plugin/plugin.json b/plugin-variants/gbrain-daily/.claude-plugin/plugin.json
index 6a4f896419..c5c3a21197 100644
--- a/plugin-variants/gbrain-daily/.claude-plugin/plugin.json
+++ b/plugin-variants/gbrain-daily/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain-daily",
- "version": "0.60.730.0",
+ "version": "0.60.731.0",
"description": "Personal knowledge-brain daily use: meetings, tasks, briefings, reading, research. Published as the gbrain-daily marketplace variant. (persona variant of the gbrain plugin — 20 skills)",
"author": {
"name": "Garry Tan",
diff --git a/plugin-variants/gbrain-daily/.codex-plugin/plugin.json b/plugin-variants/gbrain-daily/.codex-plugin/plugin.json
index 92348bb1e7..de62d94009 100644
--- a/plugin-variants/gbrain-daily/.codex-plugin/plugin.json
+++ b/plugin-variants/gbrain-daily/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain-daily",
- "version": "0.60.730.0",
+ "version": "0.60.731.0",
"description": "Personal knowledge-brain daily use: meetings, tasks, briefings, reading, research. Published as the gbrain-daily marketplace variant. (persona variant of the gbrain plugin — 20 skills)",
"author": {
"name": "Garry Tan",
diff --git a/plugin-variants/gbrain-daily/README.md b/plugin-variants/gbrain-daily/README.md
index 9f01693efd..27fc14fb13 100644
--- a/plugin-variants/gbrain-daily/README.md
+++ b/plugin-variants/gbrain-daily/README.md
@@ -1,4 +1,4 @@
-<!-- gbrain-plugin-tree-stamp: 0.60.730.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.731.0 -->
# gbrain-daily (generated persona variant — do not hand-edit)
Personal knowledge-brain daily use: meetings, tasks, briefings, reading, research. Published as the gbrain-daily marketplace variant.
diff --git a/plugin/README.md b/plugin/README.md
index 8ec89299f9..5438bc3016 100644
--- a/plugin/README.md
+++ b/plugin/README.md
@@ -1,4 +1,4 @@
-<!-- gbrain-plugin-tree-stamp: 0.60.730.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.731.0 -->
# gbrain plugin skill tree (generated — do not hand-edit)
This tree is the curated skill set for the gbrain Codex and Claude Code
diff --git a/src/core/behavior-changes.generated.ts b/src/core/behavior-changes.generated.ts
index 87eed353a2..e138256af3 100644
--- a/src/core/behavior-changes.generated.ts
+++ b/src/core/behavior-changes.generated.ts
@@ -89,6 +89,7 @@ export const RELEASED_BEHAVIOR_CHANGES: ReadonlyArray<{ since: string; id: strin
{ since: '0.60.725.0', id: 'launcher_records_bun_gst2784', text: "gbrain's hook launcher (<config dir>/hook-launcher/gbrain-hook), which every MCP server entry and hook gbrain setup writes starts gbrain through, now records the Bun that installed gbrain and puts it first on PATH. Before, a Codex session started without bun on its PATH (the desktop app, a launcher, a terminal opened before the shell profile changed) could not start gbrain serve or its hooks, and showed no tools. gbrain post-upgrade rewrites the launcher in place, and gbrain setup codex does the same; no config.toml, hooks.json or trust entry changes. gbrain doctor reports a launcher that records no Bun, or a Bun that is gone. The compiled gbrain binary needs no Bun and its launcher does not change." },
{ since: '0.60.725.0', id: 'notifier_sync_disabled_gst2515', text: "The commit notifier now honours a source's sync setting: a source with sync turned off (config.syncEnabled=false) is no longer synced when HEAD moves, and a retry it owed is dropped. An explicit sync request (a sync trigger or webhook) still runs once; if that run fails, the notifier waits for a new request instead of retrying it. To have commits sync that source again, turn sync back on with gbrain sources set-sync <id> on." },
{ since: '0.60.726.0', id: 'transcript_archive_default_gst2768', text: "On a personal brain the conversation archive is now on: the maintenance pass (the idle upkeep of an agent's gbrain serve, gbrain maintain --unattended or its schedule, and autopilot) writes one redacted page per conversation per local day from your Claude Code, Codex, OpenClaw, Hermes and Grok sessions, plus a day index, into the conversations source, then fills in older days a capped run at a time. To turn it off, run gbrain transcripts archive off (pages already written stay). A shared team brain is only offered the archive and stays off until its owner runs gbrain transcripts archive on. On a keyless brain nothing leaves this machine. With an embedding key, the archived text of new days is sent to that provider to be embedded, like any new page (unattended upkeep caps that at maintenance.embed_daily_usd; autopilot and a managed brain's write coordinator embed new pages as they arrive); older history is written keyword-only and its embedding waits until you see the price with gbrain embed --held --dry-run and approve it. No facts are extracted and no Dream synthesis runs on archive pages. gbrain doctor --only transcript_archive_freshness says whether the archive is keeping up." },
+ { since: '0.60.731.0', id: 'stable_important_three_classes_gst2818', text: "The stable channel now moves within a day only for a security fix, a data-loss fix or a fix for a regression in a release that is already on stable. Everything else, a fix that only unblocks one setup included, waits for the weekly move; if you need such a fix sooner, install its release by tag (docs/STABILITY.md, \"Pinning a version\")." },
];
/** The release of every marked id, so a function row dated releasedIn(id) takes the release that disclosed it. */
@@ -179,4 +180,5 @@ export const BEHAVIOR_CHANGE_RELEASES: Readonly<Record<string, string>> = {
launcher_records_bun_gst2784: '0.60.725.0',
notifier_sync_disabled_gst2515: '0.60.725.0',
transcript_archive_default_gst2768: '0.60.726.0',
+ stable_important_three_classes_gst2818: '0.60.731.0',
};
diff --git a/templates/bootstrap/template-repo/README.md b/templates/bootstrap/template-repo/README.md
index 081d22e1f0..bf2ee82f72 100644
--- a/templates/bootstrap/template-repo/README.md
+++ b/templates/bootstrap/template-repo/README.md
@@ -1,6 +1,6 @@
# gbrain agent workspace — template
-<!-- gbrain-template-stamp: 0.60.730.0 -->
+<!-- gbrain-template-stamp: 0.60.731.0 -->
This repository is the **"Use this template"** distribution artifact for a
[gbrain](https://github.com/garrytan/gbrain) personal-agent workspace — the same