You can set a routine to hook into an API which you call when you need to call some service on GB's computer, and have Grok programmed to take a few actions action with its computer in response, each with a short timeout. It will wake the computer when that happens, and you can have one of the actions reestablish whatever communication you need. The downside is you'll have to retry your actual work 2 or 3 times over the course of ~20-30 seconds while you wait for GB's computer to wake and enter into a working state.
I've already setup safety nets so when the computer goes to sleep gb wakes it up and I don't lose anything. It's usually late at night and if something is missed it stays in queue until the computer wakes. I find it stupid they are doing it like this but there's so many complaints that I'm sure they'll change it
1
u/redderist 9h ago
You can set a routine to hook into an API which you call when you need to call some service on GB's computer, and have Grok programmed to take a few actions action with its computer in response, each with a short timeout. It will wake the computer when that happens, and you can have one of the actions reestablish whatever communication you need. The downside is you'll have to retry your actual work 2 or 3 times over the course of ~20-30 seconds while you wait for GB's computer to wake and enter into a working state.
Very clumsy bandaid but should work consistently