native support for screen (and tmux?) about automation HOT 3 OPEN

We could either write a wrapper around ... or we could add native support ...

I am not sure if its worth the effort. Its a nice idea indeed.
But how many of use need this and how often?
I need it once after an mkcloud host booted. Not sure about other peoples use cases.

Adding such a feature should be doable, but I guess we have other more pressing issues to address.

One remaining question is how to handle non-interactive invocations, e.g. if you were batch-starting 10 new clouds in parallel.

Please, can you give us some of such machines ...

from automation.

But how many of use need this and how often?

Answering that question is the whole point of writing use cases, so you could look through the use cases I helpfully suggested and decide for yourself ;-) Probably the most important one is protecting against network outages, which explains why you don't personally feel the urgency, because you're not a remote worker.

Please, can you give us some of such machines ...

We already have one; it's called blacher.

from automation.

Probably the most important one is protecting against network outages,

Well, you might wonder that the first thing I do when running an mkcloud run is to start screen.
I also like to be able to dis- and reonnect. Even we have network outages sometimes.

My point was not to question the use of screen/tmux at all. I just wonder if its worth doing it automatically. The fix is just a screen<Enter> away. For me that currently works and does not slow me down.

So if $somebody provides such a feature I will accept it for sure. I would just not invest time into it right now (just MHO).

from automation.