You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
list_changes: what was created, changed or deleted since a date, and by which client
#8517
We send a weekly "what changed in the shared brain" note. Per page, gbrain history / get_versions has everything. Across the brain, list_pages updated_after shows only each page's latest state: no deletes, no actor, and no count of revisions in the window. get_ingest_log holds at most 50 entries and has no date filter. So the roundup either misses things or depends on a changelog page that agents have to keep by hand.
What does the solution look like?
gbrain changes --since <date> [--until] [--source] [--client] [--json] and a read-scoped MCP list_changes, built on the version history gbrain already stores. Each row: slug, created/updated/deleted, revision, time, and the principal or client that wrote it. Dream and cycle runs could add one summary row each (pages created, merged, retired).
Alternatives considered
A hand-kept changelog page. Agents forget, and it duplicates what versions already record.
Polling list_pages updated_after and diffing locally. It misses deletes and intermediate revisions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
What problem does this solve?
We send a weekly "what changed in the shared brain" note. Per page,
gbrain history/get_versionshas everything. Across the brain,list_pages updated_aftershows only each page's latest state: no deletes, no actor, and no count of revisions in the window.get_ingest_logholds at most 50 entries and has no date filter. So the roundup either misses things or depends on a changelog page that agents have to keep by hand.What does the solution look like?
gbrain changes --since <date> [--until] [--source] [--client] [--json]and a read-scoped MCPlist_changes, built on the version history gbrain already stores. Each row: slug, created/updated/deleted, revision, time, and the principal or client that wrote it. Dream and cycle runs could add one summary row each (pages created, merged, retired).Alternatives considered
changelogpage. Agents forget, and it duplicates what versions already record.list_pages updated_afterand diffing locally. It misses deletes and intermediate revisions.All reactions