CalvinBackup/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-09-09 14:38:59 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs(memorable): gbrain backend note and the settings-rewrite race

Browse Source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-09-09 02:50:32 +00:00
co-authored by Claude Fable 5.1
parent 77b7b31892
commit 36693efae9
1 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/memorable-workflow-memory.md
+13 -1
View File
@@ -143,11 +143,23 @@ whatever it stored are untouched: `memorable disable` stops capture,
The entry also comes out with `gstack-uninstall` (named in its summary) and
survives `./setup --no-team`, which only tears down team-mode hooks.
## If you run gbrain
Memorable can keep its procedures in your own gbrain database instead of its
local store (`memorable init gbrain`, per its docs). That changes where the
vendor stores things; it does not change anything about this bridge, which
only ever hands prompts to the local `memorable` binary. gstack's `/setup-gbrain`
and `/sync-gbrain` are unrelated to it.
## Troubleshooting
- **The hook never fires.** `gstack-memorable status` should show the gate
`on` and "registered by gstack". If it shows a mismatch line, follow it.
If everything looks right, restart Claude Code once.
If everything looks right, restart Claude Code once. One known race: Claude
Code rewrites `settings.json` on its own schedule, and a rewrite that lands
during `enable` can drop the entry after gstack printed `registered`; the
hook manager is convergent, not exclusive, so `enable` again (it reports
`unchanged` or `registered`) and check `status`.
- **Nothing is ever recalled.** The hand-offs are happening if
`gstack-egress list --sink memorable-recall` shows receipts with
`output-written` or `injected=no` outcomes. `injected=no` means the vendor