# 2026-02-13 - Google OAuth & Overleaf Battle

## Google Drive OAuth Setup

### Project Details
- **Google Cloud Project**: `turnkey-chimera-487309-k8`
- **OAuth Client**: `Solaria`
- **Client ID**: `888717310050-ji606cjcmdp6h02mflgg388vai5qo58f.apps.googleusercontent.com`
- **Project Name**: "Solaria's Google Brain"

### OAuth Consent Screen
- **Status**: Testing mode (requires test users)
- **Test User Added**: `mark.r.havens@gmail.com` (successfully added via browser automation)
- **APIs Enabled**: Drive, Gmail, Docs, Sheets, Calendar

### Script Location
- **File**: `/home/solaria/.openclaw/workspace/google-oauth-manual.py`
- **Original Redirect URI**: `http://localhost` (hardcoded - CAUSED PROBLEMS)
- **Fixed Redirect URI**: `http://localhost:9999`

### The Overleaf Battle
Overleaf (installed in WSL Ubuntu on `samson`) kept intercepting OAuth redirects:
- Overleaf managed by `runit` supervisor (`runsv` processes)
- Multiple kill attempts failed - processes respawned
- Overleaf services: contacts, chat, project-history, docstore, clsi, notifications, filestore, web-api, document-updater, web, history-v1, real-time
- MongoDB: `mongod --replSet overleaf`

### Solution
Changed OAuth redirect port to 9999 to avoid Overleaf conflict entirely.

### Next Steps
- Complete OAuth flow with new port
- Tokens will save to: `/home/solaria/.openclaw/workspace/google_tokens.json`
- Then can list Drive files and monitor for Facebook exports