Grok Bot computer unusable: host process leaks memory until it's killed, Update doesn't replace machine (Ticket T-I16486 )

Hey @Sam11,

This is a known issue we’re already tracking, and I’ve added your report to it. On some Grok Bot computers the background host process keeps growing after each restart until the computer runs out of memory, and it appears linked to computers that hold a very large number of files.

Updating only moves your computer to a new machine after confirming your files are safely saved, so nothing should be lost. While the computer keeps running out of memory that save can’t finish, so Update deliberately leaves the computer where it is. That’s why the uptime never changed.

Reset and Recover also carry your files over to the new machine, and with this issue that step hasn’t been finishing. When it doesn’t finish the old computer is kept, so your files are still there, but you don’t get a fresh machine either. Holding off on more Reset attempts for now makes sense.

One thing that would help: did any of your bots start creating or downloading a large number of files around Oct 17 (for example package installs, scraped pages, caches or datasets)?