CLAUDE_CONFIG_DIR is an optional env var which tells Claude Code to read configs from another directory. I use this to isolate my personal configs from shared company configs. I also use it as a way to test my integrations against company defaults.
It would be nice if rtk init either respected CLAUDE_CONFIG_DIR or supported another way to direct where the installation should happen.
$ rtk init -g
RTK hook installed/updated (global).
Hook: /Users/joshua/.claude/hooks/rtk-rewrite.sh
RTK.md: /Users/joshua/.claude/RTK.md (10 lines)
CLAUDE.md: @RTK.md reference added
Patch existing /Users/joshua/.claude/settings.json? [y/N]
y
settings.json: hook added
Backup: /Users/joshua/.claude/settings.json.bak
Restart Claude Code. Test with: git status
filters: /Users/joshua/Library/Application Support/rtk/filters.toml (template, edit to add user-global filters)
$ echo $CLAUDE_CONFIG_DIR
/Users/joshua/myclaude
CLAUDE_CONFIG_DIRis an optional env var which tells Claude Code to read configs from another directory. I use this to isolate my personal configs from shared company configs. I also use it as a way to test my integrations against company defaults.It would be nice if
rtk initeither respected CLAUDE_CONFIG_DIR or supported another way to direct where the installation should happen.