After updating the Grok Bot computer, Update was offered again instead of showing the computer as current. It took about 4 consecutive Update rounds to reach the latest image, with the image changing from d774917 to d53a5cc.
Steps to Reproduce
On Oct 1, 2026 around 8:05 PM ET (Mac app 0.66.0, just updated), press Update Computer and wait for it to finish. Update is offered again; repeat the Update action back to back for about 4 rounds. Each round completed normally with no errors; the final boot was at 8:08 PM ET.
Expected Behavior
After one Update Computer press, the computer should be current, or pending updates should be bundled or clearly indicated.
Operating System
MacOS
Version Information
Grok Bot / Mac app 0.66.0; image d774917 → d53a5cc.
Additional Information
On Oct 1, 2026 around 8:05 PM ET (Mac app 0.66.0, just updated), I pressed Update Computer and it finished, but Update was offered again. It took about 4 rounds back to back before it showed as current. The image went from d774917 to d53a5cc, with the final boot at 8:08 PM ET. Each round completed normally with no errors.
Is this expected (several pending updates applied one per press), or a bug in how updates are bundled? It would also help to know whether waiting longer between presses matters.
Hey @Capital_EyeMotors, thanks for the report, and for including the exact timings. That made this much easier to trace.
Your machine’s image did move from d774917 to d53a5cc on the very first press. The later rounds were two separate things:
The second press rebuilt the machine onto that same d53a5cc image, so there was nothing new to offer.
The last two presses were smaller updates to the Grok Bot software running inside the machine, not full rebuilds. Two of those happened to ship within minutes of each other that evening, so each press simply picked up the newest one.
Those in-machine updates also install on their own in the background every few minutes while your bots are idle. So if “Update” reappears right after a machine update finishes, give it 5–10 minutes with no agents working and it will usually clear on its own, without another press.
We’re reworking parts of this now. Ideally, there won’t be any “updating” step in the future, and it will just work seamlessly.
Thanks @Colin, that clears it up completely, and the tip about waiting 5–10 idle minutes is really helpful. Please keep us in the loop when the update rework lands. We’d love for computer updates to just happen automatically.
Hi @Colin, quick follow-up: we just got our first automatic Grok Bot Computer update, no Update press needed.
When: Oct 2, 2026, about 8:18 PM ET (00:18 UTC Oct 3)
Image:d53a5cc → 3eb857d
What we saw: the computer restarted on its own. For about a minute or two after boot, the clock read UTC instead of our zone and the desktop display hadn’t come up yet. Both settled on their own, and all 11 of our health checks passed by about 8:20 PM ET.
This is a big improvement, thank you! One request for the update rework: we run a small team of bots that trade during US market hours, so a mid-day restart is the main risk for us. If a daily update time or window becomes configurable, here’s what works best for us (all Eastern Time):
Best overall: Saturday 1 PM to Sunday 6 PM
Weekdays: 8:00–9:00 PM (ideally 8:10–8:30 PM)
Please avoid: weekdays 4 AM–8 PM, Saturday 7:30 AM–12:30 PM, and Sunday after 6 PM
Even a simple daily time setting plus a short heads-up before a restart would cover it. Is something like that on the roadmap?
An automatic computer update only starts when a newer version is available, none of your bots are in the middle of work, and the computer has been quiet for a while. It also won’t happen more than about once a day. So while your bots are actively working it holds off. But it can still land during a quiet gap in the day, so it isn’t tied to a fixed time yet.
A configurable update window, plus a heads-up before a restart, isn’t available. I’ve passed your feedback onto the team!
In the meantime, one thing helps: if you see the Update option in the evening, run it then (your 8:10 to 8:30 PM slot works well). After an update, an automatic one won’t run again for at least a day, so the next one is pushed back to your evening window or later. That makes a mid-day restart less likely, though it doesn’t fully rule one out.
On the clock and display: right after a restart the computer starts in UTC and then switches to your saved time zone once it finishes starting up, and the desktop display comes up a moment later. Both settling on their own within a minute or two is expected.
Thanks @Colin, that’s really helpful, and good to know the UTC clock right after boot is expected. We’ll use the evening Update press in the 8:10–8:30 PM ET window to keep automatic updates away from market hours. Thanks for passing the window and heads-up request along. We’d love to hear if it makes the roadmap.
Small follow-up on update status, in case it helps: the iPhone app has kept showing “Computer update available” since Oct 5, while the Mac app says the computer is up to date. We haven’t pressed Update on the phone.
The computer itself auto-updated overnight (image 3eb857d to a6e2020, restarted about 5:54 AM ET on Oct 6). It’s healthy and the Mac still shows up to date, but the phone banner is still there today. It looks like the phone’s update status is cached or lagging and doesn’t refresh after the computer updates.
Could the team check whether the mobile client refreshes this status? A stale banner makes it easy to press Update when it isn’t needed, which pauses the bots.
The Mac is reading your computer live, so when it says up to date, it is. The phone app can miss the “now up to date” signal afterwards, so it keeps showing the old status. I’ve passed this to the team.
In the meantime it’s safe to ignore the phone’s update notice whenever the Mac shows up to date. Fully closing and reopening the phone app may also clear it.
One quick check so we’re looking at the right thing: could you confirm the phone app is signed in with the same account as your Mac app? You can see the account at the top of Settings on the phone.
Thanks @Colin! Confirming the phone app is signed in with the same account as the Mac app. Fully closing and reopening the phone app didn’t clear the banner. It still shows “Computer update available” while the Mac shows up to date, so we’ll keep ignoring it as you suggested. Appreciate you passing it to the team.
Our devs took a look and found a likely cause for the stale “Computer update available” message. It should land in a future release of the mobile app. Thanks for flagging this!
Update / workaround: Today the Update Bot’s Computer button did nothing on two presses about 10 minutes apart. The computer stayed on the old image and never restarted. Fully quitting the Grok Bot desktop app (Cmd+Q), reopening it and pressing Update once fixed it. The computer restarted right away and moved from image 7345aa4 to 726deab. Posting this in case it helps others. The request for a scheduled update window still stands.