gwslisted

# gws Google Workspace operations through the official `gws` CLI. This is the local safety wrapper and workflow guide; use the CLI for execution and load references only for multi-step recipes. ## Multi-Account Model Upstream removed native multi-account support in v0.7.0 (`--account`, `gws auth list`, `GOOGLE_WORKSPACE_CLI_ACCOUNT` no longer exist - do not use them). Accounts are isolated by config directory instead: - Account registry: `~/.config/vd/gws-accounts/<alias>.gws-account.md` - one file per account declaring email, domain, timezone, and its config dir. See `references/account.gws-account.example.md`. - Credentials: one dir per account under `~/.config/vd/gws/<alias>/`, selected via `GOOGLE_WORKSPACE_CLI_CONFIG_DIR`. - The default `~/.config/gws` holds no credentials by design: a bare `gws` call fails with exit code 2 instead of silently using an ambiguous account. Every command is prefixed with the account's config dir: ```bash GOOGLE_WORKSPACE_CLI_CONFIG_DIR="$HOME/.config/vd/gws/<alias>" gws <service> ... ``` ### Account resolution 1. List configured aliases: `ls ~/.config/vd/gws-accounts/` and read the file for the chosen alias. 2. If the user named an account (alias or email), use it. 3. For reads where context makes the account obvious (work domain vs personal), pick it and state which account you used. 4. For writes, or when ambiguous: ask which account, or echo the chosen account and get confirmation. 5. Before any mutating operation, verify the liv