2026-02-01.md

/home/ubuntu/.openclaw/workspace/memory/2026-02-01.md

2026-02-01

Set up Google Calendar access on EC2 via gog (Google Workspace CLI).
OAuth redirect used loopback callback on the machine running gog:
- Example redirect: http://127.0.0.1:38957/oauth2/callback
- If opening the auth URL on a laptop while gog auth add runs on EC2, the callback hits the laptop, not EC2.
- Fix: SSH local port forward from laptop to EC2:
  - ssh -L 38957:127.0.0.1:38957 ubuntu@<ec2-host>
After auth, gog stores refresh tokens in an encrypted keyring:
- Prompt: Enter passphrase to unlock "/home/ubuntu/.config/gogcli/keyring"
- Unlock often applies per-process/session; new gog invocations may prompt again.
gog configuration observed:
- gog auth keyring file writes /home/ubuntu/.config/gogcli/config.json with { "keyring_backend": "file" }, but it may still prompt for a passphrase to unlock the keyring.
For running gog interactively while keeping it unlocked:
- Consider running gog inside a persistent tmux session, unlock once, then reuse that session.

Pending:

Decide desired UX: interactive-only vs automation.
If automation needed: consider dedicated automation Google account/shared calendar, or secret-store-based passphrase unlock.