Thanks for the info. I ran those commands (here is a snip from my history: 66 xcrun python3 -m pip install --user --ignore-installed macholib 67 export PATH=.:$PATH:/Users/khampton/Library/Python/3.9/bin 68 ech $PATH 69 echo $PATH 70 xcrun python3 -m pip install --user --ignore-installed future 71 lldb 72 lldb 73 lldb /Library/Developer/KDKs/KDK_15.1_24B83.kdk/System/Library/Kernels/kernel I have only installed Xcode 16.0 (16A242d) on this volume, which is running Sequoia 15.1 - all squeaky clean I think. I was initially using a host running older software and had the same problem. That one had been used as a dev system and I would not have been surprised if the reason it had the same problem was due to the Xcode confusion you describe. But prior to the upgrade (from Sonoma) to 15.1 on my m3 MBP, I had never installed Xcode on this host volume