I use grim, primarily. There is a wrapper of grim and slurp called “grimshot” which is very pleasant to use.

Piping slurp into grim is a one-liner in my sway config. Do you really need a wrapper around this?

Are you sure? On GNOME on Wayland? It works with Sway because of https://github.com/flameshot-org/flameshot/blob/master/docs/... but last I heard GNOME refuses to implement this.

Does it not require re-approving the access to the screen every single time?

I am on Fedora 35 and that was the case just a few weeks/months ago. They locked down the screenshot API to only the GNOME screenshotter.

Huh, and here I am on the other side wanting exactly that (different dist and DE though) but haven't gotten that part figured out yet, everything seems to have access by default... Seems end-user accessible docs still have some gaps eh (:

A lot of the parts about when and how the user is asked for permission is a Wayland compositor dependent implementation details.

E.g. while sway works well it tends to not ask the user and just grants permission as it doesn't really have it's own "HUD" (it has a default task parts, but that just a default program you could run if you want to, there are also other programs).

It's also one of the things which makes most sense to be part of the "HUD" interface of the Wayland compositor so not making it a implementation details doesn't make much sense sadly.