This looks incredibly cool and useful — providing an early example of a "blended experience" — such that your authenticated context is carried from the remote party and unified within Slack so that you can see the information that you have access to see, even if the file, information, or remote context is private.
Why is this significant? Well, one of the things we've lost in migrating from the desktop to the cloud is a unified user-authenticated context for apps to play in. On the desktop, you didn't need to sign in to every app that you use (that's changing though), or explicitly authorize each app to have access to other files (although recent iterations of operating systems have locked down access to contacts and other sensitive information). Instead of jumping through an authorization step, you can simply drag and drop — and through the magic of file formats and disk I/O (rather than web APIs) — you can share and move files seamlessly.
In the cloud, every service has to be pre-registered with every other service and then, in addition, get user authorization to move files or take action on behalf of the user.
Earl, it seems, is an attempt to collapse some of the contexts that keep you from accessing richer descriptions and information that you already have access to, and brings it into a shared working context.
Raycast