[Bug] File picker unable to resolve symlinks outside project directory

Resolved 💬 6 comments Opened Dec 19, 2025 by jonasporto Closed Feb 14, 2026

Bug Description

I am having issues on my workflow, and it seems to be due to file picker stopped to work with symlinks or symlinks outside the main project folder, it was working good on the prior version.

The file picker (@ autocomplete) no longer follows symlinks that point outside the project directory.

Setup:

  • I have symlinks in my project root pointing to a shared documentation directory:
  • .claude → ../shared-docs/.claude
  • CLAUDE.md → ../shared-docs/CLAUDE.md
  • AGENTS.md → ../shared-docs/AGENTS.md
  • This allows me to share documentation across multiple projects and git worktrees

Expected behavior:

  • When typing @.claude/ or @CLAUDE, the file picker should show files from the symlinked directories with fuzzy search
  • This worked correctly in previous versions

Current behavior:

  • Symlinked files/directories don't appear in file picker results
  • Only files physically inside the project directory are shown
  • Note: Claude Code can still READ the symlinked files via tools - only the file picker is affected

Workarounds attempted:

  • additionalDirectories setting - doesn't make symlinked paths appear in picker
  • Custom fileSuggestion command - works but loses fuzzy search capability
  • Hard links instead of symlinks - not portable (Windows/Linux) and doesn't sync new files

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 2.0.73
  • Feedback ID: a3e3876b-f88f-4abe-9f77-345277e57ea8

Errors

[]

View original on GitHub ↗

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