Skip to content

Garry's Opinionated OpenClaw/Hermes Agent Brain

TypeScript

Release v0.60.718.0

garrytanc79f67baacfe
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index 7acf354dee..5ab6959492 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain",
- "version": "0.60.717.0",
+ "version": "0.60.718.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 cf0cb2da3a..ec5d802c9f 100644
--- a/.codex-plugin/plugin.json
+++ b/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain",
- "version": "0.60.717.0",
+ "version": "0.60.718.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 9ed5309fa0..f5b5e0079e 100644
--- a/BOOTSTRAP_FOR_AGENTS.md
+++ b/BOOTSTRAP_FOR_AGENTS.md
@@ -1,4 +1,4 @@
-<!-- gbrain-runbook-stamp: 0.60.717.0 -->
+<!-- gbrain-runbook-stamp: 0.60.718.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 192eee73ee..933f0f956b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,29 @@ 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.718.0] - 2026-11-14
+
+**Three ways a commit could reach the remote past the push secret scan are closed, and the scan can no longer be skipped.** In a managed root that sits in a subfolder of its repository, a commit could change that root's own `.gbrain-scan-allow` (for example to allow every path) and be pushed along with the secret it hid; it is now held for review like one at the top level. A strict (`canonical: git`) source's commit is now trusted only when its files are exactly what gbrain wrote, so anything a Git clean filter added is scanned. Git replace refs can no longer slip files into a page-write commit the scan trusts. `commitAndPush` also lost its unscanned mode, so no caller and no push handed over from a busy publish lock can publish without the scan; it reads only the commits the remote lacks, fetching a missing remote-tracking branch first.
+
+<!-- behavior-change: managed_push_scan_every_publish_gst2650 -->
+
+### Fixed
+- In a managed root below its repository's top level, the allowlist's path globs match paths relative to that root.
+- A strict-source commit made before this release that is still unpushed is scanned once when it is pushed.
+- A page-write commit whose staged file another process reset at the same moment is no longer reported as committed with the old content; the write fails and is retried.
+- The shared-checkout guide says that an uncommitted `.gbrain-scan-allow` is honoured, because it is the user's own answer to the scan.
+
+**On a source whose pages are canonical in Git, a fact the Google loops extraction finds for an entity with no page that an exact page rule names is now refused before anything is stored, the way `remember` already refused it.**
+
+### Fixed
+
+- On a `canonical: git` source, a commitment fact for an entity with no page under an exact page rule (`gbrain access rule add --slug people/bob-example --readers alice-example`) used to be stored in the database only, with no file or commit holding it, so a rebuild from Git lost it. Once `memory/unattributed` existed, the same write was refused instead, with a message that named `memory/unattributed` rather than the entity. The write is now refused `git_home_required` (reason `facts_lane`) before any row is written, and the message and fix name the entity's page to create. An access state the database role cannot read refuses `access_policy_pending` (retry), and that message now names the entity too.
+- The loops job still records the loop. Its log line reads `[loops_extract] fact projection failed … (git_home_required)` (or `(access_policy_pending)`) and names the entity's page, so an operator can see which page to create.
+- Sources that are not strict, brains with no Git repository, and fact writers that do not keep a fallback entity behave as before.
+- Facts an earlier version already stored this way are untouched: `gbrain repair facts-home --source <id>` lists them as `folder_restricted` (`page_rule`) and its apply leaves them; creating the entity's page lets the `extract_facts` upkeep step fence them.
+
+<!-- behavior-change: strict_fallback_refusal_gst2635 -->
+
## [0.60.717.0] - 2026-11-14
### Saving a fact to a holding page is faster and keeps less history
diff --git a/VERSION b/VERSION
index 1046fe5f22..ac65e9db4b 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-0.60.717.0
+0.60.718.0
diff --git a/changelog.d/capy-push-scan-review-gaps.md b/changelog.d/capy-push-scan-review-gaps.md
deleted file mode 100644
index e3fcd6ad7f..0000000000
--- a/changelog.d/capy-push-scan-review-gaps.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-important: security
----
-
-**Three ways a commit could reach the remote past the push secret scan are closed, and the scan can no longer be skipped.** In a managed root that sits in a subfolder of its repository, a commit could change that root's own `.gbrain-scan-allow` (for example to allow every path) and be pushed along with the secret it hid; it is now held for review like one at the top level. A strict (`canonical: git`) source's commit is now trusted only when its files are exactly what gbrain wrote, so anything a Git clean filter added is scanned. Git replace refs can no longer slip files into a page-write commit the scan trusts. `commitAndPush` also lost its unscanned mode, so no caller and no push handed over from a busy publish lock can publish without the scan; it reads only the commits the remote lacks, fetching a missing remote-tracking branch first.
-
-<!-- behavior-change: managed_push_scan_every_publish_gst2650 -->
-
-### Fixed
-- In a managed root below its repository's top level, the allowlist's path globs match paths relative to that root.
-- A strict-source commit made before this release that is still unpushed is scanned once when it is pushed.
-- A page-write commit whose staged file another process reset at the same moment is no longer reported as committed with the old content; the write fails and is retried.
-- The shared-checkout guide says that an uncommitted `.gbrain-scan-allow` is honoured, because it is the user's own answer to the scan.
diff --git a/changelog.d/capy-strict-fallback-refusal-gst2635.md b/changelog.d/capy-strict-fallback-refusal-gst2635.md
deleted file mode 100644
index 276191dff5..0000000000
--- a/changelog.d/capy-strict-fallback-refusal-gst2635.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-important: data-loss
----
-
-**On a source whose pages are canonical in Git, a fact the Google loops extraction finds for an entity with no page that an exact page rule names is now refused before anything is stored, the way `remember` already refused it.**
-
-### Fixed
-
-- On a `canonical: git` source, a commitment fact for an entity with no page under an exact page rule (`gbrain access rule add --slug people/bob-example --readers alice-example`) used to be stored in the database only, with no file or commit holding it, so a rebuild from Git lost it. Once `memory/unattributed` existed, the same write was refused instead, with a message that named `memory/unattributed` rather than the entity. The write is now refused `git_home_required` (reason `facts_lane`) before any row is written, and the message and fix name the entity's page to create. An access state the database role cannot read refuses `access_policy_pending` (retry), and that message now names the entity too.
-- The loops job still records the loop. Its log line reads `[loops_extract] fact projection failed … (git_home_required)` (or `(access_policy_pending)`) and names the entity's page, so an operator can see which page to create.
-- Sources that are not strict, brains with no Git repository, and fact writers that do not keep a fallback entity behave as before.
-- Facts an earlier version already stored this way are untouched: `gbrain repair facts-home --source <id>` lists them as `folder_restricted` (`page_rule`) and its apply leaves them; creating the entity's page lets the `extract_facts` upkeep step fence them.
-
-<!-- behavior-change: strict_fallback_refusal_gst2635 -->
diff --git a/openclaw.plugin.json b/openclaw.plugin.json
index 7e69a2f0d2..ecf5c1f4cc 100644
--- a/openclaw.plugin.json
+++ b/openclaw.plugin.json
@@ -1,7 +1,7 @@
{
"id": "gbrain-context-engine",
"name": "gbrain",
- "version": "0.60.717.0",
+ "version": "0.60.718.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 0fd666bc07..b7866e295a 100644
--- a/package.json
+++ b/package.json
@@ -260,7 +260,7 @@
"bun": ">=1.4.4"
},
"license": "MIT",
- "version": "0.60.717.0",
+ "version": "0.60.718.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 70a2df0190..af3249246f 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.717.0",
+ "version": "0.60.718.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 86d75d2459..2b9cc99a4b 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.717.0",
+ "version": "0.60.718.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 005cacd144..11f030fe51 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.717.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.718.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 43fb181be9..d22ac9961e 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.717.0",
+ "version": "0.60.718.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 0c11732165..b92b34fe70 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.717.0",
+ "version": "0.60.718.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 5dbc88b965..e393d993da 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.717.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.718.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 dcf885f68e..bb2e8c4b22 100644
--- a/plugin/README.md
+++ b/plugin/README.md
@@ -1,4 +1,4 @@
-<!-- gbrain-plugin-tree-stamp: 0.60.717.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.718.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 02d37b8900..9085121b0a 100644
--- a/src/core/behavior-changes.generated.ts
+++ b/src/core/behavior-changes.generated.ts
@@ -63,6 +63,8 @@ export const RELEASED_BEHAVIOR_CHANGES: ReadonlyArray<{ since: string; id: strin
{ since: '0.60.716.0', id: 'audit_secrets_escaped_encoded_8265', text: "The opt-in high-entropy assignment detector now also catches a credential whose key quote is escaped (`{\\\"password\\\":\\\"…\\\"}`, JSON inside a JSON string, with up to three backslashes) and one after a URL-encoded separator (`password%3D…`, `token%3A…`). The value stops before an escaped closing quote and, after an encoded separator, before the next `%26` parameter; a URL-encoded URL value is treated as a reference, not a secret. `gbrain doctor` asks once for a fresh `gbrain transcripts audit-secrets` run: it is read-only, makes no model or network call, and on a 5 MB synthetic transcript took about a third of a second. Transcripts imported from now on redact both shapes. Pages imported before are not rewritten; the audit lists the ones that hold such a line as affected." },
{ since: '0.60.717.0', id: 'holding_page_versions_gst2497', text: "A holding page (memory/unattributed, or a folder's <folder>/memory/unattributed) now keeps only its newest five saved versions, whatever their size, as large pages already did. `get_versions` and `gbrain revert` see only those five. Every fact row on the page is kept, the page itself still holds every row, and Git keeps every state of the page where the brain has a repository. An older holding page sheds its extra versions in batches of at most 100 on its next saves, so nothing runs on upgrade. Once a version is removed, an `as_of` read of the page reports incomplete history, and `gbrain repair unwithdrawn-facts` lists that page's candidates as ambiguous: restore them with `--include-ambiguous` and the hash of that preview. Nothing to run." },
{ since: '0.60.717.0', id: 'owner_room_marks_gst2639', text: "A harness can now declare the group chat an answer goes into (the X-Gbrain-Room header, request-level _meta.room, or a room tool argument once whoami shows features.room). The caller's read is unchanged; every page and fact in the answer is marked room_access with whether the people in that chat could have read it, and the room_above_level notice tells the agent to keep those items out of the reply. A call with no room is unaffected. With mcp.strict_params set to reject, every tool schema now also declares the optional room argument. See docs/guides/rooms.md." },
+ { since: '0.60.718.0', id: 'managed_push_scan_every_publish_gst2650', text: "Every push gbrain makes is now scanned for secrets with no opt-out: `commitAndPush` no longer has an unscanned mode, so a push handed over from a busy publish lock is scanned too. Only the commits the remote lacks are read, and a missing remote-tracking branch is fetched first instead of scanning the whole history. In a managed root below the repository's top level, a commit changing that root's own `.gbrain-scan-allow` is held like one at the top level, and its path globs match paths relative to that root. A strict (canonical: git) source's commit whose files a Git clean filter changed is scanned instead of trusted, and so is one made before this release that is still unpushed; either is still pushed when the scan finds nothing. Git replace refs no longer change what a page-write commit holds. A false positive in an unpushed commit holds the push with `publish_secret_found` naming the file, line and rule, never the value: add its fingerprint to `.gbrain-scan-allow`, then run `gbrain sources writer retry-effects <source> --parked-pushes`, or the push fix `gbrain doctor` names." },
+ { since: '0.60.718.0', id: 'strict_fallback_refusal_gst2635', text: "On a source whose pages are canonical in Git (`canonical: git`), a fact the Google loops extraction (or any writer that keeps a fallback entity, writeSingleFact) finds for an entity with no page that an exact page rule names is now refused `git_home_required` (reason `facts_lane`) before anything is stored, with a fix that creates the entity's page; before, it was stored in the database only, with no file in Git, or refused with a message naming memory/unattributed. When the access rules cannot be read the write refuses `access_policy_pending` (retry), and that refusal's message now names the entity, for `remember` too. The loops job still records the loop and logs the refusal code with the entity's page; nothing is stored for that fact. Facts stored the old way are not changed: `gbrain repair facts-home` lists them as `folder_restricted`. Sources that are not strict and brains with no Git repository are unchanged." },
];
/** The release of every marked id, so a function row dated releasedIn(id) takes the release that disclosed it. */
@@ -127,4 +129,6 @@ export const BEHAVIOR_CHANGE_RELEASES: Readonly<Record<string, string>> = {
audit_secrets_escaped_encoded_8265: '0.60.716.0',
holding_page_versions_gst2497: '0.60.717.0',
owner_room_marks_gst2639: '0.60.717.0',
+ managed_push_scan_every_publish_gst2650: '0.60.718.0',
+ strict_fallback_refusal_gst2635: '0.60.718.0',
};
diff --git a/templates/bootstrap/template-repo/README.md b/templates/bootstrap/template-repo/README.md
index d3f632be1a..a01a188c53 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.717.0 -->
+<!-- gbrain-template-stamp: 0.60.718.0 -->
This repository is the **"Use this template"** distribution artifact for a
[gbrain](https://github.com/garrytan/gbrain) personal-agent workspace — the same