codegraph install ignores CLAUDE_CONFIG_DIR and CODEX_HOME environment variables

[seanchann]

Description

When running codegraph install, the installation process ignores custom path configuration set via the CLAUDE_CONFIG_DIR and CODEX_HOME environment variables. The tool consistently falls back to installing and writing files directly to the user's home directory (~/).

Steps to Reproduce

• Set custom environment variables:

export CLAUDE_CONFIG_DIR="/custom/path/to/claude_config"
export CODEX_HOME="/custom/path/to/codex_home"

• Run the installation command:

codegraph install

• Check the target directories.

Expected Behavior

codegraph install should read and respect CLAUDE_CONFIG_DIR and CODEX_HOME to determine where to place configuration files and runtime artifacts.

Actual Behavior

The installation hardcodes or defaults to ~/ (e.g., ~/.claude or ~/.codex), completely ignoring the exported environment variables.

Environment

OS: Linux

[maxmilian]

This is two independent halves, and one of them already has a PR that isn't linked here.

CLAUDE_CONFIG_DIR — covered by #1029 (@borfast), open since 2026-06-27 and rebased onto current main on 2026-08-25, waiting on review. It predates this issue by two months, which is why neither references the other. It resolves the global Claude config dir from the env var and follows Claude Code's own placement rule for .claude.json (beside ~/.claude by default, inside the profile dir when CLAUDE_CONFIG_DIR is set).

CODEX_HOME — nothing existed, so I've put up #1633. configDir('global') in the Codex target was path.join(os.homedir(), '.codex') with no env lookup, so the install lands in the default profile while Codex reads the override. It doesn't error — the files are written correctly, Codex just never looks at them, which is the silent-no-op shape you described. Resolution now mirrors what the copilot-cli target already does for COPILOT_HOME; the project-local layer (#1531) is unaffected and there's a test pinning that.

#1633 deliberately does not touch targets/claude.ts, so it and #1029 don't collide. Landing both closes this issue.

One thing your report didn't mention that's worth knowing: the same silent-no-op applies to detect(), so codegraph install would also have told you the target wasn't configured yet even when your real profile had it. That's covered too.