Skip to content

fix(claude-code): rename the directory plugin to everme-memory - #26

Merged
alwaysday1 merged 1 commit into
mainfrom
chore/rename_claude_directory_plugin
Nov 12, 2026
Merged

alwaysday1 merged 1 commit into
mainfrom
chore/rename_claude_directory_plugin

Conversation

@alwaysday1

Copy link
Copy Markdown
Collaborator

Summary

Renames the Claude directory plugin from everme to everme-memory.

The hook plugin that evercli installs is also named everme, with an MCP server named everme. When both plugins are installed, Claude Code logs Skipping duplicate hook registration for plugin "everme" and registers the hooks of only one of them. plugin:everme:everme then resolves to the local stdio server of the hook plugin, so the directory plugin's hooks call the wrong server.

Changes:

  • .claude-plugin/marketplace.json and plugins/claude-directory/.claude-plugin/plugin.json: name everme-memory.
  • hooks/hooks.json: every server is plugin:everme-memory:everme; the matcher that skips the plugin's own tools is ^(?!mcp__plugin_everme-memory_everme__).*.
  • README.md: correct install command (/plugin marketplace add EverMind-AI/EverMe, then /plugin install everme-memory@evermind) and the server name to select in /mcp.

The version stays 0.1.0: the plugin has not been submitted to the directory yet, and under the new name it is a new plugin.

If you installed everme@evermind from this marketplace, uninstall it, install everme-memory@evermind, and sign in again with /mcp.

Test plan

  • claude plugin validate plugins/claude-directory --profile directory passes
  • claude plugin validate . passes
  • No headers in .mcp.json, no executable files, versions match in both manifests
  • Claude Code with the everme hook plugin and everme-memory loaded together: both register their hooks, the directory hooks reach only their own server, recall injection works, tool calls and the final reply are saved, and the plugin's own mem_search call is not saved

🤖 Generated with Claude Code

The hook plugin that evercli installs is also named everme and has an
MCP server named everme. With both installed, Claude Code registers
the hooks of only one plugin named everme, and plugin:everme:everme
resolves to the local stdio server of the hook plugin, so the
directory hooks call the wrong server.

Rename the directory plugin to everme-memory. Point the hooks and the
matcher that skips the plugin's own tools at
plugin:everme-memory:everme. Fix the install command in the README.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@alwaysday1
alwaysday1 merged commit 7a612ea into main Nov 12, 2026
7 checks passed
@alwaysday1
alwaysday1 deleted the chore/rename_claude_directory_plugin branch November 12, 2026 02:28

@gloryfromca gloryfromca left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No blockers; this can merge as far as I am concerned.

Reviewed the four-file change against the PR's recorded base be7bba4 (the PR merged while this review was in progress). I covered the repository instructions, the diff, surrounding Claude Code plugin/server naming, callers and references, commit history, compatibility with the separately installed everme hook plugin, test weakening, and the plugin/MCP architecture constraints.

The rename is consistent across both manifests, every hook target, the self-tool exclusion matcher, and the installation/sign-in instructions. It removes the duplicate plugin identity while preserving the remote MCP server name. I found no concrete failure worth raising.

Verification:

  • git diff --check be7bba4...c51e973: passed.
  • Manifest/hook namespace consistency check: passed.
  • claude plugin validate plugins/claude-directory and claude plugin validate .: passed with the existing warning that this local Claude CLI does not recognize privacyPolicyUrl; this CLI does not support the author's --profile directory option.
  • npm ci: completed; audit reported 0 vulnerabilities.
  • TMPDIR=/dev/shm npm test --workspaces --if-present: passed. The initial run against /tmp failed only because the root filesystem was full (ENOSPC); rerunning the unchanged suite on available tmpfs passed.
  • GitHub CI: all reported checks passed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants