Bug: File names with # char is not properly escaped when tagging it (ENOENT) #11790

Activity

1. eersnington

   added

   bugSomething isn't workingSomething isn't working

   on Feb 2, 2026
2. github-actions

   assigned

   rekram1-node

   on Feb 2, 2026
3. github-actions commented on Feb 2, 2026

   

   github-actionsBot

   on Feb 2, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be related to existing special character handling issues. Please check:

   • Write tool JSON parsing error with large files and special characters #11630: Write tool JSON parsing error with large files and special characters

   The underlying issue may be related to how special characters (including #) are escaped in file paths when used with the @ tagging syntax.

   If this is a distinct issue from the Write tool problems, it should be addressed separately in the file tagging/parsing logic.
4. saksham1341 commented on Feb 3, 2026

   

   saksham1341

   on Feb 3, 2026

   More actions

   Have tried a fix for this by updating lineRange parsing and ensuring URI encoding of the file url to handle special characters like #.
5. yudgnahk

   added 4 commits that reference this issue on Feb 3, 2026

   fix: properly encode file URLs with special characters (anomalyco#11790)

   ...

   51ee6a0

   fix: properly encode file URLs with special characters (anomalyco#11790)

   ...

   0b86aeb
6. adamdotdevin

   closed this as completedin #12424on Feb 6, 2026