Hey, thanks for adding more detail, especially around the timing and logs.
@fablau, @tdeckers - your cases are a bit different from what we were discussing earlier in this thread. If Grok Bot is always in the foreground, the machine is caffeinated, the display stays on, and in @tdeckers’s case it’s Linux with no sleep or lock and the app runs as a single process with no restart, that doesn’t really match the “away” behavior after being idle without focus. This looks like a separate variation, and it’s worth tracking on its own.
So we don’t mix it into this thread, @tdeckers - could you please start a separate thread for the Linux case? You already have a great write-up with timestamps, so just move it there. And @fablau, if you can, please include this in a separate thread too: the app version, OS, and an excerpt from ~/.grokbot/local-exec-daemon.log with the disconnect timing and the moment the bot tried to reach the machine. That’ll make it easier for the team to separate this case from away-park.
@gshall - using Tailscale as a workaround sounds totally valid, thanks for sharing that.
I’ll post here on the main case once there’s an update.