You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I manage multiple Google Workspace accounts from the same machine:
Work email (org domain)
Personal Gmail
Client/project-specific accounts
With gws, I can only authenticate one account at a time. In practice, I need to hit different APIs with different accounts in the same workflow — e.g., read email from work account, update a sheet owned by a personal account, check calendar on a client domain.
Current Workaround
Manually swapping GOOGLE_WORKSPACE_CLI_CONFIG_DIR or GOOGLE_WORKSPACE_CLI_CREDENTIALS_FILE env vars per command, which is fragile and breaks automation.
Proposed Solution
Support named profiles/accounts, similar to how aws configure --profile or gcloud config configurations work:
# Login with named accounts
gws auth login --account work
gws auth login --account personal
# Use per-command
gws gmail users messages list --account work --params '{"userId": "me"}'
gws sheets spreadsheets get --account personal --params '{"spreadsheetId": "..."}'# Or set a default
gws auth default work
Why This Matters
For AI agent workflows especially, the agent often needs to operate across accounts (e.g., read from one Google Sheet owned by account A, send an email via account B). A first-class multi-account model would make gws viable as the single Google CLI for power users and agent systems.
This is the single most important feature in the entire suite. Everything else can be achieved by existing connectors.
My current workaround is havening multiple instances of https://workspacemcp.com running in parallel with a lot of glue code. It's not fun and reliable.
Activity
anaslimem commentedon Mar 7, 2026
@sqrrrl can i start working on it ?
parthsdoshi commentedon Mar 9, 2026
Looks like #85 is related/merged.
Edit: nvm, reverted in #253
anaslimem commentedon Mar 9, 2026
Actually, after I wrote that comment i saw that for now they won't accept PR from non collaborators temporarily.
shankscoder commentedon Mar 9, 2026
Any info on why it was reverted? Really useful feature, curious why it was removed.
anaslimem commentedon Mar 9, 2026
TBH i dont personally know why, but you can open a discussion and they will answer you.
deep-ink-ventures commentedon Mar 9, 2026
This is the single most important feature in the entire suite. Everything else can be achieved by existing connectors.
My current workaround is havening multiple instances of https://workspacemcp.com running in parallel with a lot of glue code. It's not fun and reliable.
shankscoder commentedon Mar 9, 2026
FWIW I'm using
gogcli(https://github.com/steipete/gogcli) right now as that supports multi-account auth, and works really nicely.