Fix local PC “connected” but Shell says temporarily unreachable

On Grok Bot 0.43 (Windows), the Computers list can show your local PC as connected, Local execution can be Always allow, and every agent Shell still fails with temporarily unreachable (sometimes then disconnected). Staff on local PC connected but temporarily unreachable confirmed the PC was connected and commands did reach it — the reply came back in about 11 seconds, while the agent stops waiting at 10 seconds, so the UI marks the run unreachable.

Related failures (other how-tos)

• Renaming the computer (accents vs plain letters) does not fix it.
• Toggling Local execution again is unrelated, per staff.
• This is distinct from “local machine isn’t connected” / leftover daemon: Fix Grok Bot local-exec daemon.
• ListMachines empty after idle is a different flap: Fix ListMachines empty after idle.
• The 0.43 wording change from “disconnected” to “temporarily unreachable” is a separate copy improvement, not proof the link got worse.

What to check on your side

Staff asked for the delay sources. Collect these before you file or re-file:

1. %APPDATA%\Grok Bot\local-exec-daemon.log (last ~200 lines; skim for personal data).
2. Antivirus / endpoint security (Windows Defender alone vs a third-party product).
3. Whether Documents, Desktop, or AppData redirects to OneDrive or a network drive.
4. VPN or corporate proxy while Grok Bot is open.

Follow-up A/B on the same thread pinned Surfshark Antivirus real-time (not VPN alone): each local command writes ps-script-<uuid>.ps1 under %TEMP%, and real-time scanning that path pushed replies past the 10s wait. Excluding %LOCALAPPDATA%\Temp with real-time still on restored ~1–2s commands. Step-by-step: Exclude Surfshark Temp so local Shell works. Any AV that slows the local-exec path past ~10s can look the same.

While the timeout is tracked

1. Keep Local execution on Always allow if you need the PC.
2. Prefer short local commands while testing.
3. If the daemon log loops desktop ownership lost / ConnectError / DeadlineExceeded, attach redacted lines when you reply on the forum — staff said they are already tracking the false-unreachable case.

Cloud-computer work can continue even when the local PC path is slow. See Troubleshooting for local-execution policy under Settings → General → Agent → Execution on Local Computer.

Pitfalls

• Do not Reset the Agent Computer for a local-timeout false negative — Reset targets the cloud computer.
• System-proxy / TUN VPN issues for the cloud computer are covered separately: Fix Grok Bot with system proxy or VPN TUN.