klask VS quick

There are also similar applications for usage with clap-rs.[1][2]

[1]: https://github.com/MichalGniadek/klask

[2]: https://github.com/grantshandy/claui

This is what https://github.com/MichalGniadek/klask was made for.

Klask is another GUI generator for clap that uses egui, but claui and klask work in different ways. Klask runs your code by running itself as a child with an environment variable to ignore its GUI, then capturing the child stdout. Claui only runs one process; it spawns your code in another thread and then reroutes all of your stdout into a buffer on each frame through shh.

If you want a simple GUI over command line tools, things like klask make that really easy.

Which is arguably a good reason Click should look for an alternative basis (though, OTOH, the reasons Click remains on optparse are, arguably, a reason that optparse, while it perhaps should not be further developed but for bug fixes, should not be considered deprecated), but in fact a lot of Python command-line programs depend on Click, so something that only works on argparse-based programs does not, in fact, support "almost any Python command line program".

Interestingly, there is a gooey-inspired GUI generator for Click-based programs: https://github.com/szsdk/quick

I might give this a go https://github.com/szsdk/quick