[BUG] Symlink Resolution Failure: Claude Code Unable to Traverse Symlinked Directory

Open 💬 15 comments Opened Apr 11, 2025 by rieger-jared

Environment

  • Platform (select one):
  • [x] Anthropic API
  • Platform: macos
  • Terminal: alacritty
  • Version: 0.2.68
  • Feedback ID: c3f75537-5be5-47f8-a46a-69c0c8c227ec

Bug Description

I have the dir ~/.claude symlinked to another dotfile repo which i store all my personal files. I'm using the command stow to symlink my home to this dotfiles repo. After doing so, Claude code is no longer able to detect the files in the dir ~/.claude. this sucks as now i can't checkin my claude files and have git to revise them.

Steps to Reproduce

  1. Create a dir, call it dotfiles.
  2. In that dir place the folder .claude with the contents of ~/.claude
  3. In dotfiles/.claude/commands/ create a hello world command
  4. Use the command stow --adopt -v --target=$HOME dotfiles
  5. Use ls to confirm that that ~/.claude is successfully symlinked and that you can cat the contents
  6. open up Claude code and attempt to invoke the command
  7. You should not be able to see your commands that are located and symlinked from dot files.

Expected Behavior

Claude code should be able to follow the symlinks and read the CLAUD.md file as well as any commands

Actual Behavior

Claude code shows none of the user commands defined in ~/.claude/commands/*

Additional Context

  • running /memory and chasing the local claude file, opens the file. adding a test instruction to the local memory file through claude code works fine and outputs the test message

View original on GitHub ↗

This issue has 15 comments on GitHub. Read the full discussion on GitHub ↗