gws-setuplisted

# GWS Setup The gws CLI looks straightforward but breaks in subtle ways -- Google's OAuth flow has undocumented constraints that differ between personal and organizational accounts, and the gws tool itself has open bugs around scopes and multi-account. This procedure captures the working path and the traps discovered through real setup sessions, so you avoid the silent failures that waste hours. **Prerequisites:** gcloud CLI installed, browser access for OAuth, interactive terminal for auth steps. ## Procedure ### 1. Install gws binary - Download latest Linux x86_64 from https://github.com/googleworkspace/cli/releases - Place in `~/.local/bin/`, `chmod +x` - Verify: `gws --version` ### 2. Add Google account to gcloud - `gcloud auth login <email> --no-launch-browser` (interactive terminal required) - This adds alongside existing accounts -- does NOT replace them - After login, restore work account: `gcloud config set account <work-account>` ### 3. Create or select GCP project - Check existing: `gcloud projects list --account=<email>` - Create new: `gcloud projects create gaia-<name> --name="Gaia <Name>" --account=<email>` - Naming: `gaia-<identifier>-personal` or `gaia-<identifier>-work` ### 4. gws auth setup - `gws auth setup --project <project-id>` - TRAP: When selecting scopes, DO NOT use presets ("Recommended" or "Read Only") -- they include organizational scopes that break for @gmail.com accounts ### 5. Scope selection (CRITICAL) For safe scopes and blocked s