Repository navigation
Grok Bot routines are blocked while connected to tailnet #1145
Description
After install the Tailscale plugin, routines, webhook triggers are stopped running. Each failed with:
"The helper was stopped because this agent's computer is connected to its owner's tailnet, so it only runs what the owner sends it themselves."
The tailscale-setup skill says owner-scheduled routines and linked teammates are allowed on a personal tailnet, so this looks unintended.
Observed 2026-10-31 (UTC+8): hourly and daily routines failed from about 06:10 onward. They ran again only after I removed the tailnet.
Expected: owner-created routines and messages from the owner's own agents keep running while a personal tailnet is connected.
Activity
philwhln commentedon Nov 2, 2026
Just found mine has been down all weekend. No bot message, no alert, just quiet failures.
ericgyl817 commentedon Nov 2, 2026
The team is fixing this issue and we'll report back once it's fixed thank you
ericgyl817 commentedon Nov 4, 2026
@linroex @philwhln This is fixed. Since Nov 3, routines you schedule, and the subagents they start, keep running while your personal tailnet is connected. If a routine still stops with this message, reply here with the time (UTC) and we'll take a look. Thanks for reporting it.
Jabe commentedon Nov 4, 2026
@ericgyl817 Thank you, it works again! I tried to add my local nextcloud mcp over tailscale and had a little bit of new trouble:
Bot can add the connection but I can't authorize the final step. I tried all the clients (Web, Mac app, Android app) none worked. I then added an explicit allow rule that says: "May use Nextcloud (read-write) over Tailscale". Bot was then able to use the MCP. So there appears to be some more friction with the classifier and the UI. HTH! Tried around 7:30 AM Nov 4th UTC