Claude Code now sets aside fetched files instead of saving them into protected config directories or symlinked paths
When Claude Code fetches a file and its destination would land inside a protected directory, such as a git internals folder, or a hooks, tool, or agent configuration directory, or the destination is a symlink pointing outside the current working scratch area, the file is no longer written there. Instead, Claude Code shows a message explaining the file was 'set aside' rather than saved, and a new filtering step checks each candidate destination for this condition before saving.
This stops a fetched file from silently landing somewhere that could alter git behavior, hooks, or tool and agent configuration, protecting sensitive setup files from unintended changes.