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
{{ message }}
Repository navigation
bug(drive): --drive-scope=readonly still grants full read-write access #111
Using --drive-scope=readonly during auth still results in full read-write access to Drive. The flag doesn't appear to restrict permissions as expected.
After completing OAuth flow, the token still has write access to Drive.
Expected Behavior
The resulting token should only have drive.readonly scope, preventing file creation/modification/deletion.
Actual Behavior
Full read-write access is granted despite the --drive-scope=readonly flag.
Environment
gog version: v0.9.0
OS: Ubuntu (WSL2)
Additional Context
This may be related to how scopes are combined when multiple services are authorized, or the scope may not be getting passed correctly to the OAuth flow.
I'm trying to set up a secure configuration where an AI assistant can read Drive files but cannot modify them. Currently this isn't possible even with the readonly flag.
Activity
a-b13 commentedon Feb 4, 2026
Related: #110 (Gmail doesn't even have a readonly scope option yet). Both issues are about enforcing least-privilege OAuth scopes.
a-b13 commentedon Feb 5, 2026
Related: #110 (gmail readonly scope request) — both involve scope control for different services. Would be great to solve these together.
andyg2 commentedon Feb 23, 2026
Oh if only there were a read only mode!