gog skill
Goal: Get GOG CLI commands to work reliably via Clawdbot (Telegram) on a headless VPS.
Issue Observed:
What We Tried:
* Attempted
* Ran a setup script that: removed old keyring, generated new passphrase, performed
* Confirmed
* Performed full Clawdbot daemon stop & start multiple times.
* Inspected
* Modified Clawdbot's startup command to explicitly prepend
* Confirmed Clawdbot's
* Even with explicit prepend in startup, "integrity check failed" persists.
My Environment:
* Clawdbot on DigitalOcean VPS (Ubuntu Linux).
* Clawdbot Version: 2026.1.16-2.
* GOG CLI Version: v0.7.0.
* Access via SSH (PuTTY/Termius).
* Telegram channel for Clawdbot.
Issue Observed:
gog commands consistently return "integrity check failed" when executed by Clawdbot, despite working correctly in new SSH sessions after source ~/.bashrc. The GOG_KEYRING_PASSWORD environment variable appears missing from Clawdbot's child processes' runtime environment.What We Tried:
* Attempted
gateway.restart initially.* Ran a setup script that: removed old keyring, generated new passphrase, performed
gog auth add --manual OAuth, and updated ~/.bashrc and ~/.clawdbot/clawdbot.json.* Confirmed
gog works in SSH after source ~/.bashrc.* Performed full Clawdbot daemon stop & start multiple times.
* Inspected
clawdbot-gateway process environment directly, confirming GOG_KEYRING_PASSWORD was missing.* Modified Clawdbot's startup command to explicitly prepend
GOG_KEYRING_PASSWORD=....* Confirmed Clawdbot's
exec tool CAN pass env vars (tested with MY_TEST_VAR).* Even with explicit prepend in startup, "integrity check failed" persists.
My Environment:
* Clawdbot on DigitalOcean VPS (Ubuntu Linux).
* Clawdbot Version: 2026.1.16-2.
* GOG CLI Version: v0.7.0.
* Access via SSH (PuTTY/Termius).
* Telegram channel for Clawdbot.
