[BUG] wrong path in "yes, allow reading from /// from this project" prompt

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?

In executing on my plan, Claude Code found itself asking me for permission to run a command of the form

awk '/Style.*{/,/^}/' /Users/gthb/git/apiary3/node_modules/@jsfkit/types/dist/index.d.ts | grep -E "lengthy-regexp"

As usual the first option was "yes" and the second one was of the “yes, always allow” form ... but the exact option 2 had the file path ///:

Yes, allow reading from /// from this project

The lengthy regexp did not contain slashes, or anything else that looks like it might cause this. So the weird path /// was probably derived in some erroneous way from '/Style.*{/,/^}/' or from the file path.

What Should Happen?

Claude Code should already have had permission to read that, because that path is inside my project (which it has been working in for a while). But if it did need to ask permission, then the “always allow” option should have had a real path in it.

Error Messages/Logs

Steps to Reproduce

Get Claude Code to need to use an awk invocation like that. I really can't tell very well what about my project or the specific task that Claude Code was working on might cause it to generate this strange “always-allow” path.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.34 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

Terminal app is Ghostty 1.2.3, build 12214.