-
-
Notifications
You must be signed in to change notification settings - Fork 69.5k
[Bug]: openclaw webhooks gmail setup fails on native Windows with Error: spawn gcloud ENOENT #54470
Description
Bug type
Crash (process/app exits or hangs)
Summary
Summary
On native Windows, openclaw webhooks gmail setup --account [email protected] fails with:
Error: spawn gcloud ENOENT
This happens even though gcloud is installed and callable in PowerShell, gcloud.cmd exists in PATH, gog is installed and callable, and Tailscale is logged in.
Steps to reproduce
On native Windows, install OpenClaw.
Install Google Cloud SDK and confirm gcloud --version works in PowerShell.
Install gog and confirm gog --version works.
Confirm Tailscale is logged in.
Run:
openclaw webhooks gmail setup --account [email protected]
Observe:
Error: spawn gcloud ENOENT
Expected behavior
The documented openclaw webhooks gmail setup --account [email protected] flow should start the Gmail setup wizard and write the Gmail hook configuration instead of exiting with Error: spawn gcloud ENOENT.
Actual behavior
Running openclaw webhooks gmail setup --account [email protected] on native Windows immediately exits with the user-visible error: Error: spawn gcloud ENOENT.
OpenClaw version
OpenClaw 2026.3.23-2 (7ffe7e4)
Operating system
Windows (native PowerShell environment on Lenovo ThinkCentre; exact Windows build not captured during testing)
Install method
Global npm install on native Windows (openclaw resolves to C:\Users\james\AppData\Roaming\npm\openclaw.ps1)
Model
NOT_ENOUGH_INFO
Provider / routing chain
NOT_ENOUGH_INFO
Additional provider/model setup details
Issue occurs during the local Windows CLI helper flow for Gmail webhook setup, before any model invocation is reached. Relevant setup context: gcloud is installed and callable in PowerShell, gog is installed and callable, Tailscale is logged in, and where.exe gcloud resolves to valid gcloud / gcloud.cmd paths, but openclaw webhooks gmail setup --account [email protected] still fails with Error: spawn gcloud ENOENT.
Logs, screenshots, and evidence
openclaw --version
OpenClaw 2026.3.23-2 (7ffe7e4)
gcloud --version
Google Cloud SDK 561.0.0
bq 2.1.29
core 2026.03.13
gcloud-crc32c 1.0.0
gsutil 5.36
gog --version
v0.12.0 (c18c58c 2026-03-09T05:53:14Z)
Get-Command gcloud | Select-Object Source
C:\Users\james\AppData\Local\Google\Cloud SDK\google-cloud-sdk\bin\gcloud.ps1
where.exe gcloud
C:\Tools\gcloud\gcloud.cmd
C:\Users\james\AppData\Local\Google\Cloud SDK\google-cloud-sdk\bin\gcloud
C:\Users\james\AppData\Local\Google\Cloud SDK\google-cloud-sdk\bin\gcloud.cmd
Failing command:
openclaw webhooks gmail setup --account [email protected]
Observed output:
🦞 OpenClaw 2026.3.23-2 (7ffe7e4) — I'm not magic—I'm just extremely persistent with retries and coping strategies.
Error: spawn gcloud ENOENT
Additional evidence:
- Tailscale was logged in and working at the time of testing.
- `gcloud --version` succeeded in PowerShell before the failing command.
- `gog --version` succeeded in PowerShell before the failing command.
- A wrapper was also created at `C:\Tools\gcloud\gcloud.cmd` and placed first in PATH.
- Even after that wrapper was first in `where.exe gcloud`, the OpenClaw command still failed with the same `spawn gcloud ENOENT` error.Impact and severity
Affected users/systems/channels: observed on this native Windows OpenClaw CLI environment during Gmail webhook setup for Jarvis.
Severity: blocks workflow.
Frequency: reproducible in this environment; observed each time the setup command was run during testing.
Consequence: Gmail webhook onboarding could not be completed, so email intake for the agent could not be set up through the documented command.
Additional information
No last known good version was observed for this workflow on native Windows. The issue was isolated after verifying that gcloud, gog, and Tailscale were all working in PowerShell, including a PATH-based wrapper workaround for gcloud.cmd, but the documented Gmail setup command still failed with the same spawn gcloud ENOENT error.