yamanin/registry
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(claude-code): expand tilde and \$HOME in boundary config path before symlink

Browse Source 
Addresses Copilot review comment on PR #797: when ARG_BOUNDARY_CONFIG_PATH
contains a leading ~ or literal \$HOME (e.g. ~/.config/...), it was passed
as-is to ln -sf without shell expansion, resulting in a broken symlink.
Now expands both forms before creating the symlink.

Closes coder/registry#797

Generated with OpenClaw using Claude
This commit is contained in:
DevelopmentCats 2026-04-05 00:40:14 +00:00
parent 8f6853522d
commit 022fd1c0dd
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
registry/coder/modules/claude-code/scripts/start.sh
View File

@ -239,6 +239,9 @@ function start_agentapi() {
exit 1 exit 1
fi fi
elif [ -n "$ARG_BOUNDARY_CONFIG_PATH" ]; then elif [ -n "$ARG_BOUNDARY_CONFIG_PATH" ]; then
# Expand leading tilde and literal $HOME so paths like ~/.config/... work correctly
ARG_BOUNDARY_CONFIG_PATH="${ARG_BOUNDARY_CONFIG_PATH/#\~/$HOME}"
ARG_BOUNDARY_CONFIG_PATH="${ARG_BOUNDARY_CONFIG_PATH/\$HOME/$HOME}"
printf "Linking boundary config from %s to %s\n" "$ARG_BOUNDARY_CONFIG_PATH" "$BOUNDARY_CONFIG_FILE" printf "Linking boundary config from %s to %s\n" "$ARG_BOUNDARY_CONFIG_PATH" "$BOUNDARY_CONFIG_FILE"
if [ "$ARG_BOUNDARY_CONFIG_PATH" != "$BOUNDARY_CONFIG_FILE" ]; then if [ "$ARG_BOUNDARY_CONFIG_PATH" != "$BOUNDARY_CONFIG_FILE" ]; then
mkdir -p "$BOUNDARY_CONFIG_DIR" mkdir -p "$BOUNDARY_CONFIG_DIR"