0.70.2 was said to keep your computer connected when you step away

Update, Oct 13: Later on Oct 12 at 4:49 PM ET, staff member deanrie still described 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," and said "the helper doesn't start again automatically when the bot wakes up for a scheduled job." A user in that thread asked whether 0.70.2 fixed it. No staff reply has confirmed the fix on that thread yet. Another user said they are on 0.70.2 and will report back if idle drops continue. Treat mohitjain's unfocused-window fix as staff-reported and still under re-test. Screen lock and scheduled-job restart remain open. Note: 0.70.2 is a build staff have named on the forum; the changelog now lists it but doesn't mention this fix, and whether it fixes this issue is now disputed.

Update, Oct 14: Staff now say directly that no release is confirmed to fix this. On Oct 13 at 11:51 AM ET, deanrie said "I can't confirm that this version fully fixes the issue," about 0.70.2, and that the behavior "is still being tracked," including away-park, where the Mac is marked "away" after about 10 minutes without focus or when the screen is locked. At 12:59 PM ET deanrie added "I can't confirm that any specific release fully fixes this behavior" and "There isn't a separate setting to disable this behavior yet." The workaround is unchanged: bring the Grok Bot window to the front, or have your Bot do it after each job ([[entry:tip-auto-focus-grok-bot-after-jobs]]).

Staff say Grok Bot 0.70.2 stops treating your Mac or Linux computer as "away" just because the app window sat in the background. On Monday at 2:46 AM ET, mohitjain told a Linux user that "Grok Bot 0.70.2 keeps the local helper running" after the window has been unfocused for about 10 minutes. Three minutes later he told a Mac user the same build "changes this so your Mac stays connected while you're away."

What changed#

Until this build, the desktop app paused the local connection your Bots use when it thought nobody was at the computer. Before this build, kevinn listed three away triggers: the screen locks, the PC sleeps, or "The Grok Bot window stops being the active window," including a browser with grok.com open. mohitjain's Mac case was a Bot that had clicked into Godot, so Grok Bot was no longer the active window. After about 10 minutes unfocused, the helper stopped, and a Bot asking for the machine did not bring it back. 0.70.2 is meant to keep that helper running through the unfocused case.

The changelog now lists 0.70.2 (dated Oct 11, also covering 0.69.0 to 0.70.1). Its notes don't mention the unfocused-window change. A Linux 0.70.2 .deb was on Cursor's download server at 8:36 AM ET today (file date Sun Oct 11, 1:32 AM ET). One forum report from Chris_Doyle shows a version field of "0.70.2" on macOS stable, built Oct 11, while the same post's description still says App Version 0.68.1. No staff reply yet. We did not install the desktop app on this machine, so we couldn't watch the helper ourselves.

Why it matters#

Always-on Macs and Linux boxes, and any Bot that has to click into another app, could lose the local computer mid-job. Staff's earlier advice was to keep Grok Bot as the active window. This build is the first named fix for that pause.

How to use it#

1. On Mac: open Settings, Updates, Check for Updates, then Restart to Update. If it does not relaunch, fully quit with Cmd+Q and open it again.
2. On Linux, mohitjain said the apt repo "doesn't have it yet." Install the .deb he posted, then fully quit and reopen:

wget -O grok-bot_0.70.2_amd64.deb https://api2.cursor.sh/updates/download/stable/linux-x64/grok-bot-fb0a830618be0c54
sudo apt install ./grok-bot_0.70.2_amd64.deb

3. Staff have not said whether 0.70.2 changes the unfocused pause on Windows. Keep the Grok Bot window focused there until they do.
4. On Mac or Linux, leave the Grok Bot window in the background for more than 10 minutes, then ask a Bot to run a short command on that computer.

On my local computer, write the current time to /tmp/grok-bot-away-check.txt, wait 12 minutes without me touching the Grok Bot window, then append the time again. Tell me both timestamps.

Good to know#

• Staff confirmed the Mac and Linux paths. They have not said whether Windows gets the same unfocused-window fix.
• Staff asked people who still drop on 0.70.2 to reply with the times and their timezone.
• Screen lock and sleep were separate "away" triggers in earlier staff replies. Today's posts name the unfocused-window case. If your machine still drops only when locked, say so in those threads.
• The Bot's own cloud computer still pauses when no Bot is working. That is a different known issue.
• On Ubuntu 22.04-based Linux, local execution can fail for a C++ runtime mismatch even on newer builds. See the known issue.