Honor CLAUDE_CONFIG_DIR across hooks, tools, and launcher - #1943
Open
MarnuLombard wants to merge 1 commit into
Open
Honor CLAUDE_CONFIG_DIR across hooks, tools, and launcher#1943MarnuLombard wants to merge 1 commit into
MarnuLombard wants to merge 1 commit into
Conversation
- Route all 36 hooks + install tools through the resolved config root, not a hardcoded ~/.claude. - lifeos launcher self-locates its root and exports CLAUDE_CONFIG_DIR + LIFEOS_DIR to the spawned Claude. - Deploy settings.system.json (repointed on relocation) and dedup the templated command form on upgrade.
MarnuLombard
force-pushed
the
fix/hooks-honor-claude-config-dir
branch
from
August 22, 2026 14:09
543f20e to
db1caf9
Compare
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
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.
LifeOS hooks and install tools hardcoded
~/.claude, so an install under a relocated config root (--config-root/CLAUDE_CONFIG_DIR) copied files into its own root but resolved them against the global~/.claude.Worse, a SessionStart
MergeSettingshook would rewrite the GLOBALsettings.jsonfrom inside a relocated install.This routes all 36 hooks and the install tooling through the resolved config root, has the
lifeoslauncher exportCLAUDE_CONFIG_DIRso a relocated install actually runs in its own path, and closes two latent gaps:settings.system.jsonwas never deployed, and the upgrade merge did not dedup the new templated command form. Default installs are byte-identical.settings.system.json(repointed on relocation) and dedup the upgrade path.