Support $CLAUDE_CONFIG_DIR for custom config paths #349

Activity

1. zehua

   added a commit that references this issue on Mar 23, 2026

   fix: support \$CLAUDE_CONFIG_DIR for custom config paths (garrytan#349)

   ...

   bde8591
2. loocor commented on Mar 23, 2026

   

   loocor

   on Mar 23, 2026

   More actions

   Thanks for writing this up so concretely. I now have PR #364 open as the phase-1 install/runtime tranche of RFC #289:
   #364

   That PR does not add $CLAUDE_CONFIG_DIR support yet, but it does pull host layouts, discovery roots, and runtime roots into a single contract (scripts/host-registry.ts) instead of leaving them scattered across setup/templates/checks.

   So to me this issue now looks like a strong, narrow follow-up on top of that contract: config-root resolution should become part of the host path model rather than another repo-wide literal-path cleanup.

   👍React with 👍1Reacted by Zehua Liu
3. zehua commented on Mar 23, 2026

   

   zehua

   on Mar 23, 2026

   Author

   More actions

   @loocor let's figure out if the proposed fix in #351 could be merged first or be done on top of #364
4. loocor commented on Mar 24, 2026

   

   loocor

   on Mar 24, 2026

   More actions

   @loocor let's figure out if the proposed fix in #351 could be merged first or be done on top of #364

   The changes are huge, and I guess Garry won't merge it.
5. mkyed commented on Apr 28, 2026

   

   mkyed

   on Apr 28, 2026

   More actions

   Until this lands, here's a workaround that auto-applies on every /gstack-upgrade. Sharing in case it helps anyone running with CLAUDE_CONFIG_DIR set:

   A git post-merge hook in each gstack repo runs an idempotent substitution over SKILL.md and SKILL.md.tmpl, replacing ~/.claude/skills/gstack/ with the active context's path. Because the hook lives in .git/hooks/, it survives git pull and fires automatically after /gstack-upgrade.

   Script — drop this somewhere on your PATH (e.g. ~/bin/gstack-fix-paths):

   #!/usr/bin/env bash
   # Idempotent. Auto-detects context from gstack repo location.
   # Workaround for #349 / #351 until merged.
   set -euo pipefail
   
   resolve_context() {
     if [ -n "${1:-}" ]; then
       if [ -f "$1/setup" ] && [ -d "$1/bin" ] && [ -d "$1/agents" ]; then
         cd "$1/../.." && pwd -P
       else
         cd "$1" && pwd -P
       fi
       return
     fi
     local cur; cur="$(pwd -P)"
     while [ "$cur" != "/" ]; do
       if [ -f "$cur/setup" ] && [ -d "$cur/bin" ] && [ -d "$cur/.git" ]; then
         cd "$cur/../.." && pwd -P; return
       fi
       cur="$(dirname "$cur")"
     done
     echo "Could not determine context — pass gstack repo path." >&2
     return 1
   }
   
   CTX_ABS="$(resolve_context "${1:-}")"
   GSTACK_DIR="$CTX_ABS/skills/gstack"
   HOME_PREFIX="${HOME%/}/"
   TILDE_CTX="${CTX_ABS#$HOME_PREFIX}"
   [ "$TILDE_CTX" != "$CTX_ABS" ] && TILDE_CTX="~/$TILDE_CTX" || TILDE_CTX="$CTX_ABS"
   REPLACE="${TILDE_CTX}/skills/gstack/"
   
   scanned=0; patched=0
   while IFS= read -r f; do
     scanned=$((scanned + 1))
     if grep -qF '~/.claude/skills/gstack/' "$f" 2>/dev/null; then
       REPLACE="$REPLACE" perl -pi -e 's|\Q~/.claude/skills/gstack/\E|$ENV{REPLACE}|g' "$f"
       patched=$((patched + 1))
     fi
   done < <(find "$GSTACK_DIR" \( -name 'SKILL.md' -o -name 'SKILL.md.tmpl' \) -type f)
   
   echo "[gstack-fix-paths] context=$TILDE_CTX scanned=$scanned patched=$patched"

   Hook — drop this in each gstack repo's .git/hooks/post-merge, mode 755:

   #!/bin/sh
   exec "$HOME/bin/gstack-fix-paths" "$(git rev-parse --show-toplevel)"

   Verified end-to-end on v1.15.0.0: rolled back to v1.14.0.0, artificially regressed pair-agent/SKILL.md (45 hardcoded refs), ran git pull --ff-only origin main, hook fired automatically and patched 62 SKILL.md files. Idempotent — re-run patches 0.

   Tested with two parallel contexts (~/Work/.claude and ~/Personal/.claude). Uses perl -pi so it works on both BSD/macOS and GNU/Linux without the sed -i syntax difference.
6. elifarley commented on Jun 10, 2026

   

   elifarley

   on Jun 10, 2026

   More actions

   Confirming this still bites on v1.57.9.0, with the most common user-visible failure mode in case it helps prioritize:

   Under a custom CLAUDE_CONFIG_DIR, /autoplan and /codex print [codex-unavailable: auth missing] on every run even with Codex authenticated. The hardcoded source ~/.claude/skills/gstack/bin/gstack-codex-probe can't resolve, so _gstack_codex_auth_probe is never defined and ! <undefined-cmd> (exit 127) reads as an auth failure. The same mechanism silently degrades the gstack-config / telemetry / learnings calls.

   Two small notes for whoever picks this up:

   • The freshness-CI objection to the generator route (the "Option 2" rejected in fix: support $CLAUDE_CONFIG_DIR for custom config paths (#349) #351) is avoidable: commit the regenerated SKILL.md in the same change, so committed output == gen:skill-docs output and the gate passes.
   • That said, @loocor's framing looks right — config-root resolution belongs in the host path model (the RFC #289: land phase-1 host integration contract #364 / RFC: define a standard host integration contract for gstack #289 contract), not a fourth repo-wide literal-path sweep.

   Happy to help test whichever approach lands.
7. time-attack commented on Jul 15, 2026

   

   time-attack

   on Jul 15, 2026

   Last edited by time-attack

   Contributor

   More actions

   @zehua CLAUDE_CONFIG_DIR remains unsupported by the runtime path contract, and the current pull requests do not implement it safely.
8. garrytan

   added a commit that references this issue on Aug 15, 2026

   v1.64.0.0 fix wave: full tracker audit — 90 fixes, 52 issues closed, …

   ...

   008dd65
9. capy-ai commented on Oct 11, 2026

   

   capy-aibot

   on Oct 11, 2026 – with Capy AI

   Contributor

   More actions

   Thanks @zehua and everyone who confirmed this. Installs under a custom CLAUDE_CONFIG_DIR now get their own rendered skills that point at the right root (v1.91.16.0, #1882), so the /autoplan and /codex codex-probe failures from hardcoded ~/.claude paths are gone. One small leftover (setup run from outside a skills dir) is tracked in TODOS.md; please upgrade and reopen if you still see wrong-path behavior.
10. capy-ai

    closed this as completedon Oct 11, 2026