Skip to content

feat(claude-code): release the directory plugin 0.1.1 - #30

Merged
alwaysday1 merged 1 commit into
mainfrom
chore/claude_directory_plugin_0_1_1
Nov 14, 2026
Merged

alwaysday1 merged 1 commit into
mainfrom
chore/claude_directory_plugin_0_1_1

Conversation

@alwaysday1

Copy link
Copy Markdown
Collaborator

Summary

Releases the Claude directory plugin everme-memory 0.1.1. The files are identical to the internal release branch.

Changes:

  • .mcp.json: send X-EverMe-Host-Sessions: 1 on every MCP request. The server lists mem_forget_session only for clients that send this header.
  • hooks/hooks.json: pass ${session_id} as sessionKey to the recall hook, so the recall result names the session key that Claude can forget.
  • skills/everme-memory/SKILL.md: call mem_forget_session only when the user explicitly asks to forget the conversation.
  • README.md: how to forget a conversation, how to stop saving with a read-only agent, credential replacement before storage, and how EverMe keeps and deletes data.
  • plugin.json and .claude-plugin/marketplace.json: version 0.1.1.

The server side is live in production.

Test plan

  • claude plugin validate plugins/claude-directory --profile directory passes
  • claude plugin validate . passes
  • No executable files; versions match in both manifests
  • Production, full browser OAuth with a new DCR client: password sign-in, consent page, callback with code, state and iss, token exchange with all five scopes
  • Production tools/list with that token: mem_forget_session is listed with X-EverMe-Host-Sessions: 1 and not listed without it

🤖 Generated with Claude Code

Send X-EverMe-Host-Sessions on every MCP request, so the server lists
mem_forget_session for this plugin. Pass the Claude Code session id to
the recall hook, so Claude knows which session key to forget.

Tell Claude in the skill to call mem_forget_session only when the user
asks to forget the conversation. In the README, describe how to forget
a conversation, how to stop saving with a read-only agent, how EverMe
replaces credentials before it stores data, and how EverMe keeps and
deletes data.

The server side of these changes is live in production.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@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 complete origin/main...HEAD diff and relevant surrounding plugin/MCP code and history. I covered the repository's AGENTS.md rules, the changed manifests/hooks/docs/skill, host integration and backward compatibility, stable MCP names, version consistency, privacy/token-handling implications, callers, and whether tests were weakened (none were changed).

Verification:

  • npm ci: passed
  • npm test --workspaces --if-present: passed (360 tests)
  • npm audit --audit-level=moderate: passed, 0 vulnerabilities
  • JSON parsing and git diff --check: passed
  • Claude Code 2.1.247 plugin and marketplace validation: passed with the existing unchanged privacyPolicyUrl warning
  • Local Go gates could not run because Go is not installed in this environment; the PR's GitHub cli-test and all other CI checks are green
  • Worktree was returned clean and generated artifacts were removed

@alwaysday1
alwaysday1 merged commit 80d009b into main Nov 14, 2026
7 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.

2 participants