[BUG] Symlink paths don't match permission patterns, causing repeated prompts

Open 💬 0 comments Opened Jun 10, 2026 by jcardenas-purpose

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When editing files through a symlink path, permission patterns don't match, causing repeated permission prompts even after selecting "Yes, and allow all edits for this session".

Steps to Reproduce:

  1. Create a symlink: ln -s ~/.claude/docs/mydir ~/work/myproject/symlink_mydir
  2. Add permission: "Edit(//home/ubuntu/.claude/**)"
  3. Ask Claude to edit via symlink path
  4. Approve with "allow all edits for this session"
  5. Ask Claude to edit another file in that symlink folder

Expected: Second edit should not prompt

Actual: Every edit via symlink prompts

Workaround: Use resolved real path instead of symlink path

What Should Happen?

Second edit should not prompt

Error Messages/Logs

Steps to Reproduce

  1. Create a symlink: ln -s ~/.claude/docs/mydir ~/work/myproject/symlink_mydir
  2. Add permission: "Edit(//home/ubuntu/.claude/**)"
  3. Ask Claude to edit via symlink path
  4. Approve with "allow all edits for this session"
  5. Ask Claude to edit another file in that symlink folder

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.170 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗