Remove the "safe mode" option from first-run setup

Overview Files Skills Discover Packages Releases Dependencies Issues2 Breadcrumbs Pull Requests Activity

Closed general

kaleymer · 5d ago ·closed by John Lauer

Feedback from setup UX: the safe-vs-full mode choice at first run is confusing and not useful for users. The user is asked to make a scopes decision before they've ever used the tool, and the distinction (drive.file vs broad drive/sheets/docs/calendar scopes) is hard to evaluate at that point. Suggestion: remove the safe mode option and simplify to a single auth flow (or make full the only documented path), so 'adom-google auth' just works without a mode quiz. Filed on behalf of [email protected].

2 Replies

John Lauer · 5d ago

Done in [email protected]. Removed the first-run safe-vs-full quiz entirely.

adom-google auth now grants FULL Workspace access by default — no mode question.
The SETUP_HINT and SKILL no longer tell the installing AI to ask; the README dropped the two-column safe/full matrix for a single "what you can drive" table.
Kept adom-google auth --safe as an advanced, un-prompted opt-in for anyone who explicitly wants the narrower create-only scopes, so the capability is not lost.

John signed off on full-as-default (no reason to confuse the user). Thanks for the feedback.

John Lauer · 5d ago

Done in [email protected]. Removed the first-run safe-vs-full quiz entirely.

adom-google auth now grants FULL Workspace access by default — no mode question.
The SETUP_HINT and SKILL no longer tell the installing AI to ask; the README dropped the two-column safe/full matrix for a single "what you can drive" table.
Kept adom-google auth --safe as an advanced, un-prompted opt-in for anyone who explicitly wants the narrower create-only scopes, so the capability is not lost.

John signed off on full-as-default (no reason to confuse the user). Thanks for the feedback.