My Mac’s computer link shows disconnected (connected:false) for long stretches even though the Mac is awake, on AC power, online, and I’m actively using it (often chatting with Grok Bot from it). Machine Shell from my bots fails until I bring the Grok Bot window to the front, then it reconnects within a minute. It really isn’t disconnected.
Times observed (America/Chicago)
Thu Oct 8: ~6:13–6:22 PM. Chrome was frontmost until 6:21:19 PM; Grok Bot came forward and the link was back by 6:22.
Fri Oct 9: ~9:00–10:03 AM (helper log shows a connection timeout after ~2:07 AM, then nothing until the helper was replaced at 10:07:00, one second after Grok Bot came to the front at 10:06:59).
What I checked
No sleep/wake events in pmset log; on AC, display sleep off.
No Wi-Fi drops in that window.
Grok Bot holds no power assertion; macOS logged it as running but not visible while the link was down.
~/.grokbot/local-exec-daemon.log: a connection timeout, then silence until the window got focus. Built-in retry is ~10s, so a 1-hour outage isn’t normal retry behavior.
I use ProtonVPN, which may cause the initial connection reset, but recovery never happens on its own while the app is in the background.
Steps to Reproduce
Mac awake, on AC power, online (ProtonVPN on), Grok Bot app running.
Bring another app (e.g. Chrome) to the front so the Grok Bot window is in the background, and keep using the Mac normally.
Wait for the local-exec helper’s connection to drop (in my case a connection timeout in ~/.grokbot/local-exec-daemon.log).
ListMachines shows the Mac as connected:false and machine Shell from bots fails, for up to an hour or more.
Bring the Grok Bot window to the front: the helper is replaced and the Mac reconnects within about a minute.
Expected Behavior
The local-exec helper should reconnect on its own (or wake when a bot needs the machine) while the Mac is awake, without the app having to be in front.
Operating System
MacOS
Version Information
Grok Bot:
Version: 0.68.1
OS: darwin (macOS 27.0.1, build 26A434)
Hardware: MacBook Pro 16" (Mac14,10, Apple M2 Pro)
Additional Information
Impact
Scheduled bot jobs that need the Mac (hourly Teams posts) miss runs while the Mac is in use.
Related
Environment
Grok Bot 0.68.1, macOS 27.0.1, MacBook Pro 16" (M2 Pro), ProtonVPN on.
Hey, thanks for the detailed report and timings. That really helps.
What you’re describing is a known issue we’re tracking, and I’ve passed your case to the team. In short, to save resources, Grok Bot starts treating the Mac as “away” when the Grok Bot window hasn’t been in the foreground for about 10 minutes, or when the screen is locked, even if you’re actively working in other apps. While the Mac is in the “away” state and the computer goes to sleep, the app stops the local helper. Right now, the helper doesn’t automatically start again when the bot wakes up for a scheduled job, so the Mac shows as disconnected until you bring the Grok Bot window back to the foreground.
ProtonVPN isn’t the cause here. Short connection drops from it recover on their own.
Current workaround: bring the Grok Bot window to the foreground, even for a second, and the Mac should reconnect in about a minute. If you can, click into it a couple of minutes before your hourly jobs run. There’s no separate setting to turn this behavior off yet. I’ll reply in the thread when there’s an update.
I have the same problem, but interestingly enough, the problem appears even if Cursor is in the foreground all the time and the computer is caffeinated and the display is on all the time.
Same issue on Linux (Ubuntu 25.04, GNOME/Wayland), Grok Bot 0.68.1.
The machine is always on: suspend disabled, no screen lock, no suspend/resume in the journal, wired link up the whole time. The Grok Bot app ran as one process from 9 Oct 22:42 and never crashed (bootOutcome “ready”). Yet the computer showed as disconnected to my bots for hours: 10 Oct ~09:26–09:58, and from before 17:00 on 10 Oct until 10:49 on 11 Oct (CEST).
~/.grokbot/local-exec-daemon.log shows the app sending the local-exec daemon SIGTERM and only starting a new one when I came back to the machine. The new daemon started at 10:49:53, 4 seconds after my first input. Bots asking for the computer in between did not bring it back, so a scheduled job that needed the machine failed all evening.
Expected: either keep the daemon running while the app is open on a desktop that never sleeps, restart it when a bot needs the machine, or offer a setting to opt out of the “away” shutdown.
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.
I am going to open a new thread about my specific issue, but your suggested log (local-exec-daemon.log) doesn’t include any timing information. I’ll post the part that most likely is related to the disconnection issue.
Same issue here. Grok Bot 0.68.1, MacBook Pro M1 Max, macOS 27.0.1. I run several bots that use my Mac, and they keep getting “local machine isn’t connected” while the app says it’s fine.
Drops I’ve logged (CT):
Oct 10: ~2:30 PM, 3:03 to 3:08, 5:57 to 6:00, 7:31 to 7:46, 8:00, 8:11 to 8:50, 9:55 to 10:05, 11:00 to 11:35 PM
Oct 11: ~1:00 AM, 1:53 to 2:30+ AM, 8:17 to 8:34, 9:52 to 10:02 AM, 2:14 to 2:21 PM
Some lined up with the screen locking. I moved the lock delay to 8 hours, which helped, but I still get drops while I’m actively using the Mac unlocked (9:52 to 10:02 AM and 2:14 to 2:21 PM on Oct 11). Wi-Fi was stable, no sleep, and the app process was running the whole time. It only comes back when I bring the Grok Bot window to the front or remote in.
Please let the local helper wake back up when a bot needs it, or add a setting to keep it always on. Right now scheduled and background bot work just fails.
@RambunctiousHeathen, thanks for the detailed logs and timing info. This is exactly the issue we’re tracking, and this thread is already linked to it.
Short version: to save resources, Grok Bot starts treating the Mac as away when the Grok Bot window hasn’t been in the foreground for about 10 minutes, or when the screen is locked, even if you’re actively using other apps. While the Mac is in the away state and the computer goes to sleep, the app stops the local helper. Right now, the helper doesn’t start again automatically when the bot wakes up for a scheduled job, so the Mac shows as disconnected until you bring the Grok Bot window to the foreground. The fact that increasing the lock delay helped fits this pattern. The screen no longer locks and triggers away as often, but the 10-minute out-of-focus rule still remains, which is why you still see drops while actively working.
Current workaround: bring the Grok Bot window to the foreground, even just for a second, and the Mac should reconnect within about a minute. If you can, click into it a couple of minutes before the hourly job starts. Another option, which @gshall shared above, is to use Tailscale on the machine so it doesn’t depend on whether the app is in focus.
There isn’t a separate setting to turn this behavior off yet. I’ll post in this thread when there’s an update.
On 0.68.1, local-exec dropped after the Grok Bot window was in the background ~10 minutes (or after screen lock), stayed down while chat still worked, and only came back when someone brought the app to the front. Matches the “away” behavior Dean described.
We are on 0.70.2 now. Staff noted in a related thread that 0.70.2 keeps the Mac connected while away — we will report back here if idle drops continue on this build.
Hey, about 0.70.2: I can’t confirm that this version fully fixes the issue. The behavior we discussed in this thread is still being tracked. That includes away-park, where the Mac is marked as “away” after about 10 minutes without focus on the Grok Bot window or when the screen is locked, and the local helper does not start back up on its own after wake for a background task. I don’t have evidence that this was fixed in any specific release.
If you’re already on 0.70.2, the best next step is to update and watch it for a couple of days in your normal setup, especially with background or hourly tasks and the window out of focus. If the drops happen again, please send the time with timezone and a short snippet from ~/.grokbot/local-exec-daemon.log from around that moment. I’ll match it with what we’re seeing on our side.
@xufeng, thanks for following up on 0.70.2. That’s a really helpful retest.
For now, the workaround is still the same: bring the Grok Bot window to the front, even for a second, and the Mac should reconnect in about a minute. The option from @gshall to use Tailscale on the machine also works if you need it to be independent of app focus. There isn’t a separate setting to disable this behavior yet. I’ll post in the thread once I have an update.
Awesome, thank you. My bot seems to be running just fine and never losing connection. What I did implement, though, was instructions for the bot to automatically bring the Grok bot application on the Mac to the front after launching any job. I can’t confirm yet if I turn that off, it will still continue to work. I can confirm that I’ve had no issues even when it was bringing the Grokbot program to the front from the foreground. It was still losing connection, fully caffeinated, and the screen was never sleeping (no screensaver, etc.). It seems to be good for now but I’ll run a quick test, put the Grokbot application behind another window or something, and see what happens
Glad it’s working consistently now. Your approach makes sense: bringing the Grok Bot window to the front after the job starts is basically the same workaround we recommend, just automated. As long as the window gets focus from time to time, the local helper stays alive.
On versions, I can’t confirm that any specific release fully fixes this behavior. We’re still tracking away-park, where the Mac gets marked as “away” after about 10 minutes without window focus or when the screen is locked.
Your test would be helpful: turn off the auto bring-to-front behavior, put Grok Bot behind another window, and let a couple of normal background or hourly job cycles run. If the drops come back, send the time with timezone and a short snippet from ~/.grokbot/local-exec-daemon.log from that moment, and I’ll compare it with what we’re seeing on our side.
There isn’t a separate setting to disable this behavior yet. I’ll post in the thread when there’s an update.