I use trogon to run a script that communicates with some flaky services, so it will fail on a not-infrequent basis, and I need to run it again to recover.
With a normal bash command, I can scroll through history and just find the command with all the correct options to run it again.
But when using trogon, this will only take me back to the command where I run the tui. Instead, I have to find the stdout from the trogon run, then copy and paste the command, and edit it to take out any extra newlines (because it's just a raw string), before I can actually run the command.
If trogon had a "print" instead of run command, this would let me avoid that process. This mode would also be useful for inclusion in other scripts and workflows.