I've done that and can relate to the problem! It's common for Kubernetes, where you never know which cluster kubectl is pointing to. The Target (what we can where you are running things), is one of the options in the CLI. So you have to at least provide: the Target and the script to run a command. This way you always know where you are running things, it's something like this:

runops tasks create --target mysql-demo --script 'select * from dundermifflin.customers;

Ah, great, thanks. Some of the wording made it sound like perhaps it was hooked transparently. This appears very clear.