Hey folks, I’m trying to connect a Gmail account to OpenClaw via Gmail Pub/Sub

[astral spire]

Hey folks, I’m trying to connect a Gmail account to OpenClaw via Gmail Pub/Sub hooks and I’m stuck on the gog dependency.

What I already did:

• Created a Google Cloud project
• Enabled Gmail API and Drive API
• Created OAuth credentials
• Saved client secret locally
• Ran openclaw webhooks gmail setup --account [e-mail] successfully

That setup completed and configured:

• project
• Pub/Sub topic
• subscription
• push endpoint

But when I run:

openclaw webhooks gmail run --account [e-mail]

I get:

gog not installed

What I found so far:

• OpenClaw docs say Gmail hooks require gog / gogcli
• OpenClaw code appears to reference https://github.com/steipete/gogcli
• The installed binary name seems to be gog

My problem:
I need the exact current install source and install command for the gog binary that openclaw webhooks gmail run expects.

Could someone confirm:

1. the correct repo/package
2. the correct Linux install command
3. whether the binary should be named gog
4. whether there’s any extra auth/bootstrap step required after install

I’m running OpenClaw on Linux and trying to wire up [e-mail].

Thanks.

[sharp flicker]

Let me verify against the actual docs and source so I don’t hand you a made-up install command.

I checked the current docs + source on 2026.4.9.

1. Repo/package

   • On Linux, the current install source in the docs is GitHub releases from steipete/gog
   • Some places still say gogcli, but OpenClaw actually looks for the gog binary

2. Linux install command

   • Docs show this pattern:

   curl -L https://github.com/steipete/gog/releases/latest/download/gog_Linux_x86_64.tar.gz \
     | tar -xz -C /usr/local/bin && chmod +x /usr/local/bin/gog
   

   • On a normal Linux host, you’ll usually want:

   curl -L https://github.com/steipete/gog/releases/latest/download/gog_Linux_x86_64.tar.gz \
     | sudo tar -xz -C /usr/local/bin
   

   sudo chmod +x /usr/local/bin/gog
   command -v gog
   gog --version

3. Binary name

   • Yes, it should be named gog
   • OpenClaw source checks ensureDependency("gog", ["gogcli"]) and then runs spawn("gog", ...)

4. Extra auth/bootstrap

   • Yes, gog needs its own one-time auth setup if you haven’t done it already:

   gog auth credentials /path/to/client_secret.json
   gog auth add [e-mail] --services gmail
   gog auth list
   

• On headless Linux / containers, you may also need GOG_KEYRING_PASSWORD set

One extra gotcha, if setup succeeded but run says gog not installed, that often means a PATH mismatch. Check command -v gog as the same user/environment that runs openclaw.

Docs:

• https://docs.openclaw.ai/cli/webhooks
• https://docs.openclaw.ai/automation/cron-jobs#gmail-pubsub-integration

If you want, paste:

openclaw --version
command -v gog
gog --version

and I can sanity check the exact next step.

[astral spire]

Is it different on a mac?

[sharp flicker]

Yep, a bit.

On macOS:

• Install method is Homebrew
• Formula is steipete/tap/gogcli
• Binary is still gog

Use:

brew install steipete/tap/gogcli
command -v gog
gog --version

Then the auth/bootstrap is the same:

gog auth credentials /path/to/client_secret.json
gog auth add [e-mail] --services gmail
gog auth list

One useful difference: on macOS, OpenClaw’s source will actually try to auto-install missing gog via Homebrew if brew is available. On Linux, it does not auto-install, it just throws gog not installed.

So short version:

• Linux: manual install from GitHub release tarball
• macOS: brew install steipete/tap/gogcli
• Both: binary name is gog

Docs:

• https://docs.openclaw.ai/cli/webhooks
• https://docs.openclaw.ai/automation/cron-jobs#gmail-pubsub-integration

If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution, helps Answer Overflow index it for the next person.

[astral spire]

openclaw webhooks gmail run says "gog not installed" on Debian Linux.
The docs reference steipete/gog on GitHub but that repo returns 404.
What is the correct current install command for the gog binary on Linux x86_64?

[sharp flicker]

I’m going to verify the live upstream, the 404 smells like the docs are stale.

Yep, the OpenClaw docs look stale there.

Current upstream repo:
https://github.com/steipete/gogcli

For Debian Linux x86_64, the live upstream docs currently point to build from source, not the broken steipete/gog tarball.

Use:

git clone https://github.com/steipete/gogcli.git
cd gogcli
make
sudo install -m 0755 ./bin/gog /usr/local/bin/gog

Then verify:

command -v gog
gog --version

A couple important bits:

• OpenClaw expects the binary to be named gog
• The repo/package name is gogcli
• After install, auth is still needed if you have not already done it:

gog auth credentials /path/to/client_secret.json
gog auth add [e-mail] --services gmail

If you want the shortest accurate summary: