gog issue when authenticated
β
Solved
Looking at the logs, I can see the issue clearly:Summary
Gmail OAuth Token Error: The Gmail integration is failing with oauth2: "invalid_grant" "Token has been expired or revoked."
Key Points
1. User re-authenticated: At 17:15:33Z, you ran gog auth add juanpablodlc@gmail.com --services gmail,calendar,drive,contacts,sheets,docs successfully (confirmed by gog
auth list showing calendar,gmail for that account).
2. Two distinct error patterns:
- missing --account (or set GOG_ACCOUNT) - The tool invocation isn't passing the account parameter
- invalid_grant "Token has been expired or revoked." - OAuth token is expired
3. The disconnect: Even though gog CLI has valid credentials, the Clawdbot tool that calls Gmail API is likely:
- Using its own cached OAuth token (not gog's token)
- Or not properly configured to use the gog credentials
Solution
Ah, classic environment variable issue! 
The gateway runs as its own process, so it doesn't automatically inherit shell variables from your terminal. Switching from iTerm2 to Ghostty likely meant
Lessons for future:
- Gateway = separate process = separate environment
- Env vars need to be in the gateway's startup script or
- When switching terminals/shells, always check if background services need the env vars too
Good catch on the
The gateway runs as its own process, so it doesn't automatically inherit shell variables from your terminal. Switching from iTerm2 to Ghostty likely meant
~/.zshrcGOG_ACCOUNTLessons for future:
- Gateway = separate process = separate environment
- Env vars need to be in the gateway's startup script or
~/.clawdbot/clawdbot.json- When switching terminals/shells, always check if background services need the env vars too
Good catch on the
--accountGOG_ACCOUNT
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,827Members
Resources
Was this page helpful?
