Use Case
Many Google Workspace users manage multiple accounts — personal, business, client domains, etc. Tools like gog support this with an --account flag that lets you switch between authenticated accounts seamlessly:
gog gmail search "newer_than:1d" --account siraustin@gmail.com
gog calendar list --account info@business.com
Current Behavior
gws stores a single set of encrypted credentials. Running gws auth login again overwrites the existing auth, making it impossible to work with multiple Google accounts without manual credential swapping.
Proposed Solution
Add multi-account support, e.g.:
# Auth multiple accounts
gws auth login # default account
gws auth login --account work@corp.com # additional account
# Use specific account
gws gmail users messages list --account work@corp.com --params '{"userId": "me"}'
# List authenticated accounts
gws auth list
# Set default
gws auth default work@corp.com
Each account's credentials would be stored separately (encrypted), with one designated as the default.
Why This Matters
- Freelancers/consultants managing client Workspace accounts
- Users with personal + work Google accounts
- AI agents that need to operate across multiple accounts (e.g., OpenClaw bots managing email for different users)
- Anyone migrating from multi-account tools like
gog
Love the project — the dynamic Discovery Service approach is brilliant. Multi-account would make it a complete gog replacement. 🚀
Use Case
Many Google Workspace users manage multiple accounts — personal, business, client domains, etc. Tools like
gogsupport this with an--accountflag that lets you switch between authenticated accounts seamlessly:gog gmail search "newer_than:1d" --account siraustin@gmail.com gog calendar list --account info@business.comCurrent Behavior
gwsstores a single set of encrypted credentials. Runninggws auth loginagain overwrites the existing auth, making it impossible to work with multiple Google accounts without manual credential swapping.Proposed Solution
Add multi-account support, e.g.:
Each account's credentials would be stored separately (encrypted), with one designated as the default.
Why This Matters
gogLove the project — the dynamic Discovery Service approach is brilliant. Multi-account would make it a complete
gogreplacement. 🚀