Fix: Support CLAUDE_CONFIG_DIR for custom Claude installations #226
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Users with custom CLAUDE_CONFIG_DIR settings (e.g., ~/.claude_personal for multiple accounts) were unable to use claude-mem because plugin paths were hardcoded to ~/.claude. Changes: - Add MARKETPLACE_ROOT constant in paths.ts that respects CLAUDE_CONFIG_DIR - Update worker-utils.ts to use shared MARKETPLACE_ROOT - Update context-generator.ts to use shared MARKETPLACE_ROOT - Update BranchManager.ts to use shared MARKETPLACE_ROOT This allows users who set CLAUDE_CONFIG_DIR environment variable to use claude-mem with their custom Claude Code configuration directory. Fixes thedotmack#210 (partial - addresses custom config dir issue reported in comments)
majiayu000
force-pushed
the
fix/support-claude-config-dir
branch
from
748f04f to
68c8a56
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
CLAUDE_CONFIG_DIRenvironment variable for users with custom Claude Code configurationspaths.tsto avoid hardcoded~/.claudepathsProblem
Users who use custom
CLAUDE_CONFIG_DIRsettings (e.g.,~/.claude_personalfor multiple accounts) were unable to use claude-mem because plugin paths were hardcoded to~/.claude.As reported in #210 comments by @hffmnn:
Changes
MARKETPLACE_ROOTconstant that respectsCLAUDE_CONFIG_DIRMARKETPLACE_ROOTinstead of hardcoded pathMARKETPLACE_ROOTfor version marker pathMARKETPLACE_ROOTfor git operationsTest Plan
CLAUDE_CONFIG_DIR(needs user verification)Fixes #210 (partial - addresses the custom config directory issue reported in comments)