Exclude Surfshark Temp so Grok Bot local Shell works

Grok Bot can show your Windows PC as connected while every local Shell fails with temporarily unreachable. Staff on local PC connected but temporarily unreachable measured the agent wait at about 10 seconds. When the PC reply arrived in about 11 seconds, the UI still marked the command unreachable.

On that thread, Surfshark Antivirus real-time protection was the delay. Each local-exec command writes a fresh ps-script-<uuid>.ps1 under %TEMP% and runs it in PowerShell. Surfshark scanning that create/execute path pushed the round trip past the timeout.

Confirm this is your delay

1. Computers list: local PC connected.
2. Local execution: Always allow.
3. Agent Shell: temporarily unreachable (or connected → disconnected after a hang).
4. Task Manager shows local-exec-daemon running under Grok Bot.
5. You run Surfshark Antivirus with real-time protection on.

Staff asked for antivirus, VPN, OneDrive redirects, and daemon logs. The A/B on that report:

Setup	Result
Surfshark VPN on, AV real-time off	OK (~1.3s)
Web protection on, real-time off	OK (~3s)
Real-time on	temporarily unreachable (~11s vs 10s wait)
Real-time on + exclude only %LOCALAPPDATA%\Temp	OK (~1–2s)

VPN alone was not the failure once real-time was off.

Fix: exclude Temp (keep real-time on)

1. Open Surfshark Antivirus exclusions.
2. Add %LOCALAPPDATA%\Temp (or the expanded C:\Users\<you>\AppData\Local\Temp).
3. Leave real-time protection on if that exclude is enough.
4. Retry a short local command (hostname, whoami) from the Bot.

Surfshark did not accept a wildcard exclude for only ps-script-*.ps1 on that report. Excluding the Grok Bot install folder or %APPDATA%\Grok Bot alone was not enough earlier in the same thread.

If it still times out

1. Collect %APPDATA%\Grok Bot\local-exec-daemon.log (last ~200 lines; redact personal data).
2. Note other AV products, VPN, and whether Documents/Desktop/AppData redirect to OneDrive.
3. Prefer short local commands while testing.
4. File or bump the forum thread with version, OS, and the latency numbers.

Broader false-unreachable context: Fix local PC “connected” but Shell says temporarily unreachable. Do not Reset the Agent Computer for a local-timeout false negative — Reset targets the cloud computer.

Pitfalls

• Turning off all antivirus forever is a worse default than excluding Temp when A/B proves real-time is the delay.
• System-proxy / TUN VPN issues for the cloud computer are a different path: Fix Grok Bot with system proxy or VPN TUN.
• Cloud-computer work can continue while you tune local AV.