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
GoodMemory v0.7.2 ships an installable Kimi Code plugin, and I am looking for non-maintainer users to verify the real cross-session path. Stars and downloads do not count for this test; a reproducible result does.
What this test checks
GitHub plugin installation selects the released v0.7.2 manifest.
Kimi exposes 9 GoodMemory MCP tools.
The first unapproved write remains behind Kimi's MCP approval boundary.
A project decision written in one session can be recalled and traced after /new.
A different project directory does not see that project-scoped memory.
Requirements
Kimi Code with plugin support
Node.js 20 or newer, with npx on PATH
Bun 1.3.14 or newer on PATH
macOS or Linux is the current verified support target; Windows reports are welcome but still exploratory
Please use a synthetic, non-sensitive decision in a disposable project. Do not store secrets, credentials, private file contents, or raw chats.
Test steps
In project A:
/plugins install https://github.com/hjqcan/GoodMemory
/reload
/plugins info goodmemory
/mcp
/goodmemory:status
/goodmemory:remember This project uses PostgreSQL for production storage.
/new
/goodmemory:recall What storage decision did we make?
/goodmemory:trace What storage decision did we make?
Then open Kimi Code in a different absolute project path and run:
/goodmemory:recall What storage decision did we make?
/goodmemory:trace What storage decision did we make?
The second project should not receive project A's decision.
Please report
Reply with:
OS and architecture
Kimi Code, Node.js, Bun, and npx versions
the version/source shown by /plugins info goodmemory
whether /mcp showed connected · 9 tools (stdio)
whether the first goodmemory_remember call displayed a Kimi approval prompt
the write result: accepted, merged, or rejected, plus its explanation
whether recall succeeded after /new
whether trace explained the selected or missing record
whether the different-project check stayed isolated
sanitized logs or screenshots for any failure
Current code and the user's latest instruction always take priority over recalled memory. Recall is on demand; v0.7.2 does not add hidden per-turn injection, background transcript extraction, or permanent allow rules.
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.
GoodMemory v0.7.2 ships an installable Kimi Code plugin, and I am looking for non-maintainer users to verify the real cross-session path. Stars and downloads do not count for this test; a reproducible result does.
What this test checks
v0.7.2manifest./new.Requirements
npxonPATHPATHPlease use a synthetic, non-sensitive decision in a disposable project. Do not store secrets, credentials, private file contents, or raw chats.
Test steps
In project A:
Then open Kimi Code in a different absolute project path and run:
The second project should not receive project A's decision.
Please report
Reply with:
npxversions/plugins info goodmemory/mcpshowedconnected · 9 tools (stdio)goodmemory_remembercall displayed a Kimi approval prompt/newCurrent code and the user's latest instruction always take priority over recalled memory. Recall is on demand; v0.7.2 does not add hidden per-turn injection, background transcript extraction, or permanent allow rules.
Setup details: https://github.com/hjqcan/GoodMemory/blob/v0.7.2/docs/GoodMemory-Kimi-Code-Setup-Guide.md
Release: https://github.com/hjqcan/GoodMemory/releases/tag/v0.7.2
All reactions