Repository navigation
Releases
Releases · SeKondBrainAILabs/kemory-plugin
v0.17.0
Added
- A Kemory plugin for Cursor, in
plugins/cursor. It brings the hosted Kemory MCP server, thekemoryskill, and hooks that load context at session start and capture the session through the Kemory CLI. The hooks do nothing when the CLI is not installed. Do not combine it withkemory connect --host cursor, or Cursor gets every tool twice. - Session capture works under Muse Code. Muse sends no transcript path, so capture now finds its session log by session id and reads the user turns from it. Claude Code and Grok Build transcripts are read as before. The store reminder can read Muse logs too, but it stays off by default and Muse's cleared environment gives no way to turn it on yet.
- Muse Code can install the plugin.
.muse-plugin/plugin.jsonbrings thekemoryskill,/kemory:loginand/kemory:status, the hooks and the memory server. The manifest carries the same version as the Claude Code and Grok Build ones. Under Muse the rate reminder fires only after a Kemory recall tool, and the memory server no longer stands down for an entry in Claude Code's config, which Muse does not read.
Fixed
- Credential resolution and the hook helpers no longer import Python modules from the current directory. They ran their Python as inline code, which puts the working directory first on the import path, so a
json.pyin a project root ran inside the program that holds the refresh token. They now run from files in the plugin's own directory. - Session capture and the store reminder skip a transcript line of unexpected shape. A line that is valid JSON but not a message object (such as
null, a number or a list) used to stop both for the whole session; now only that line is ignored.
v0.16.0
Added
- You are told which organisation Kemory is using, by name.
/kemory:login
now ends with "Active organisation: ", and/kemory:statusshows the
same line. Signing in with no earlier credential file uses your account's home
organisation, which may not be the one you work in; until now nothing said so,
and recall and capture quietly used it. Both say how to switch:
kemory use <org-id>with the Kemory CLI. When the server cannot name the
organisation, nothing is shown and sign-in works as before.
Changed
- PRIVACY.md now names the hosted host and every endpoint each hook and command calls. A test fails when the plugin scripts use a host or endpoint the document does not name.
v0.15.4
Notes
- The README says where the memory cards come from. The card Claude shows
after a save or recall comes from the Kemory server over MCP and needs
neither plugin; kemory-panel draws its own card only in the Claude Code
terminal.
v0.15.3
Fixed
- Grok Build:
/kemory:statusno longer talks about the claude.ai
connector. On a machine that also has Claude Code it reported a claude.ai
Kemory connector and told you to check/mcp. That connector never runs in a
Grok session and Grok has no/mcp, so the check is now skipped under Grok.
v0.15.2
Fixed
- Recall and capture follow the organisation you selected with
kemory use. The CLI, and so the Kemory tools, sent the selected
organisation on every request, but the hooks sent only the token. With more
than one organisation, prompt recall read from, and session capture wrote
to, the token's own organisation while the tools used the selected one. The
hooks and the MCP bridge now sendX-Organization-IDfrom the credential
file'sactive_org_id, as the CLI does. An API key is unaffected.
v0.15.1
Fixed
- Grok Build: no restart after
/kemory:login. Grok reads a server's tool
list once, when a session starts. The bundled server used to exit without a
credential, so the memory tools only appeared after a restart. Under Grok it
now starts signed out: every tool is listed, each call answers
"run/kemory:login" until you sign in, and the first call after signing in
goes through. Claude Code is unchanged. - Grok Build:
/kemory:loginshows its link straight away. Grok does not
run a command's!`…`line, so the model used to read files to work out
how to sign in. The command now says what to do when that line does not run. - Grok Build: the plugin recognises Grok from where it is installed. Grok
does not exportCLAUDE_PLUGIN_ROOTto the shell, so inside
/kemory:statusthe disabled-server report from 0.14.0 and the
grok plugin updateadvice never appeared. Both work now.
v0.15.0
Added
- Session capture now flushes before
/compact. APreCompacthook runs
the same capture asStopandSessionEnd, for a manual/compactand for
auto-compact, so turns not yet stored are captured before the context is
summarised away instead of waiting for the session to end. It sends the same
bounded, redacted digest of your own turns, not your files or tool output,
andKEMORY_AUTO_CAPTURE=0still turns it off. The hook runs in the
background, prints nothing and always exits 0, so it can never block
compaction. - The READMEs document the Kemory server's slash commands.
/mcp__plugin_kemory_kemory__enhance <request>returns your request with
related memories cited by id, and/mcp__plugin_kemory_kemory__save-session
captures a session's decisions and durable facts before/compactor at the
end of a session. They appear when your Kemory server offers them; the
bundled bridge already relays MCP prompt, resource and completion requests
unchanged, and a test now holds it to that.
v0.14.0
Added
- Grok Build: the plugin now says when Grok has switched its MCP server off.
A server listed indisabled_mcp_serversin~/.grok/config.tomlis never
launched, and Grok's MCP Servers tab offers disabling as the only action on
a plugin's server. Until now nothing said so: the hooks kept working and the
kemory_*tools were simply missing./kemory:statusnow reports it every
time, without a "will start" tick, and a new Grok session tells the agent
once a day. The setting is read, never changed.
v0.13.3
Fixed
- The plugin no longer calls every host "Claude Code".
/kemory:login,
/kemory:statusand the MCP server named Claude Code wherever they ran, so
under Grok Build they reported on, and gave remedies for, a product that was
not running. They now describe the host they are actually in. - "How to update the plugin" names a command you can run. Under Grok Build
that isgrok plugin update kemory; it was/plugin update kemory@kemory,
which Grok has no such command for. - The claude.ai connector check is skipped where there is no Claude. With
no~/.claude.jsonthe status output said it could not read the file; it now
says nothing, rather than reporting on a product you may not use. /kemory:statusnames the right capture namespace. It reportedshared; capture writes touser:sessionsunlessKEMORY_CAPTURE_NAMESPACEsays otherwise, and the plugin docs now listKEMORY_ALLOW_DUPLICATE,KEMORY_MCP_TIMEOUTandKEMORY_CLIENT_ID.
v0.13.2
Changed
kemory-plusis nowkemory-panel. It is the same optional add-on,
Kemory's interface in Claude Code, under a name that does not read like a
paid tier. Its commands are now/kemory-panel:memories,
/kemory-panel:rememberand/kemory-panel:learned. If you installed
kemory-plus, switch with/plugin uninstall kemory-plus@kemory, then
/plugin install kemory-panel@kemory.
Fixed
- PRIVACY.md and SECURITY.md now match what the plugin does. They list the credential file
/kemory:loginwrites, every local state file, and every endpoint the plugin contacts.