gws auth login --help (and -h) is silently ignored — starts the OAuth flow instead of printing help
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #835 by @nuthalapativarun — closed without merging
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- authentication, cli
Research direction
Start at the gws auth <method> dispatch and compare it with the working top-level and helper-command help paths. Reproduce gws auth login --help, -h, and the other auth methods without triggering their real actions. Done means each auth method prints its help and exits before OAuth, setup, status, export, or logout side effects occur.
Written by the indexing model from the issue text.
Description
Summary
gws auth <method> --help (and -h) is silently ignored — the help flag does not print help, and the subcommand executes
its real action instead. This is at minimum surprising and at worst dangerous for auth login, which triggers an OAuth
flow (printing an authorization URL and waiting on stdin) when the user only intended to read the help text.
Other gws commands handle --help correctly, which makes the inconsistency the most notable part.
Reproduction
Tested on @googleworkspace/cli 0.18.1, macOS 26.4.1, Node 24.14.0.
$ gws auth login --help
Open this URL in your browser to authenticate:
https://accounts.google.com/o/oauth2/auth?scope=...&redirect_uri=http://localhost:52908&...
# → starts a real OAuth flow, binds a localhost redirect port, waits on stdin
$ gws auth login -h
# same — starts the OAuth flow
$ gws auth setup --help
Step 1/6: Checking for gcloud CLI...
✓ gcloud CLI found
# → starts the real interactive setup wizard
$ gws auth status --help
Using keyring backend: keyring
# → runs the status command
For comparison, these work correctly:
$ gws --help
gws — Google Workspace CLI
USAGE: ...
# ✓ prints help
$ gws auth # no subcommand
Usage: gws auth <login|setup|status|export|logout> [options]
# ✓ prints help (this is what `--help` should produce too)
$ gws gmail +triage --help
[Helper] Show unread inbox summary (sender, subject, date)
Usage: gws +triage [OPTIONS]
Options: ...
# ✓ prints help
So --help is honored at the top level (gws --help), at the bare-subcommand level (gws auth), and on helper commands
(gws +triage --help) — but not on any of auth login, auth setup, auth status, auth export, auth logout. The
argument parser appears to be skipped or short-circuited for the auth methods specifically.
Why this matters
gws auth login --helpis a natural thing for a user to type while exploring the CLI. Today it has the side effect of
starting an OAuth flow that binds a localhost port, opens a browser tab in some configurations, and may overwrite saved
credentials when completed. That's a footgun.gws auth setup --helpsimilarly starts the real interactive setup wizard, including gcloud probing. A user trying to
learn what flagssetupaccepts ends up walking through actual setup.- The inconsistency with the rest of the CLI (
--helpworks everywhere else) is a usability bug regardless of the side
effects.
Suggested fix
Have gws auth <method> route through the same argument parser the other subcommands use, so --help/-h short-circuits
before any side effect. The output of gws auth (the bare subcommand) is already a good template for what gws auth login --help should print.
Environment
@googleworkspace/cli0.18.1- macOS 26.4.1 (Darwin 25.4.0), Node 24.14.0
- Dominant language
- Rust
- Stars
- 32.3k
- Forks
- 2k
- Avg merge
- 16h 3m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from googleworkspace/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
googleworkspace/cli#984 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
googleworkspace/cli#983 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
googleworkspace/cli#958 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
googleworkspace/cli#921 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
googleworkspace/cli#920 ·
Maintainers usually reply within 1 day
All issues in googleworkspace/cli
Similar issues
-
area:cli area:security bug priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
status: new topic: ga4gh-sdk type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
comp-rbac
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ClickHouse/ClickHouse#131875 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug(python): read_transaction raises TypeError on a Rewrite with rewritten indicesPossibly taken @Borg93 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
lance-format/lance#11117 ·
Maintainers usually reply within 2 days