It may be best for manual refresh to be the default behavior after a job has finished.
When I view a log for a job that has more than one screen’s worth of output (most of the time), I typically try to diagnose a problem that appears at the end of the log. However, the auto-refresh occurs before there is enough time to read the relevant line near the end of the log, so I have to scroll down again.
I realize that it’s also possible to obtain the logs through the API, but for quick interactive work, being able to click into the log of a job that has just ended would be very helpful.
However, it seems that auto-refresh that is in effect by default