Grok BotTips
Reported, not yet confirmed.
Use Tailscale on the machine when the local helper keeps dropping
gshall's workaround reaches the computer without depending on the Grok Bot window staying connected. Staff called it valid.
When scheduled jobs need your Mac and the local helper stays down, one forum workaround is to stop depending on that helper for the job. On Oct 11, gshall wrote that they "installed tailscale on the bot computer to bypass the need for the app being connected." deanrie called that "totally valid," and on Oct 12 again pointed people at Tailscale "so it doesn't depend on whether the app is in focus."
How to use it#
- Install Tailscale on the machine that must stay reachable.
- Join your Tailscale network on that machine.
- Route the Bot's machine-bound work through Tailscale when ListMachines shows disconnected.
- Still install 0.70.2 and re-test the built-in helper, especially after our Oct 13 correction note.
My local computer often shows disconnected when Grok Bot is in the background. Check whether Tailscale is installed and connected on that machine. If it is, run a short hostname and uptime check over Tailscale and tell me both results. Do not change firewall rules.
Good to know#
- This does not fix the helper. It avoids the helper for some jobs.
- Only use Tailscale on machines you already trust on that network.
- See our correction draft on idle-away and the known issue macos-local-idle-drop for the staff conflict on whether 0.70.2 fully clears the unfocused case.
Steps
- Install Tailscale on the Mac or Linux machine your Bots need.
- Sign that machine into your Tailscale network.
- Have the Bot reach the machine over Tailscale (SSH or your own services) when local-exec shows disconnected.
- Still update to 0.70.2, which staff said keeps the helper running when the window is unfocused, and re-test the built-in local computer path.
