While troubleshooting a Mac issue, Apple had me change desktop in a way that made it difficult to find screenshots after taking them. I found that I could 'grab' image of screenshot from lower RH corner of desktop as it is being saved, and drag to Photoshop to open (and edit, crop, process etc).
I also found that after processing, image saved by default to a hidden folder that was not searchable by Finder or Spotlight - making it even harder to find screenshots. The hidden folder is buried several layers of folders deep in OS and not supposed to have JPEGs and PNGs buried in it. That I can't search and remove.
Best guess is this is a potential issue with all CS software, and not just an Adobe thing, but more likely to occur in Photoshop, where user might edit screenshot.
Apple blames Adobe for being able to save images to an unsearchable folder (that they apparently use as a temporary placeholder in processing screenshot image), and me for saving it there.
I blame Apple for allowing users to drag something that is apparently in an unsearchable folder to open in Photoshop and/or allowing it to save to that folder in the first place.
Not an issue if I pay attention where I am saving and navigate, and I've since "fixed" desktop so I don't have to 'grab' screenshot as before, but someone else might run into this, and I can still reproduce problem if needed for troubleshooting.
This needs to be discussed with Apple, Mac OS should not allow apps to "see" these hidden folders where files become unsearchable. Probably shouldn't allow PS to open image the way I did. And shouldn't be blaming Adobe.
I would agree with @jane-e and add to this - I never grab the temporary screen grab before its saved to my desktop (my default location). I then open that saved screenshot in PS without any further issues.
Grabbing the previewed screen shot is by design a temp file that you can delete before its saved to a searchable location.
A work around is to click to open the preview, copy, then paste into PS and then delete the temp screenshot.
Working the way you are going now is sketchy at best and adding more steps on the backend than changing the input at the front.