Skip to content

docs(google-workspace): document corporate OAuth limitation for gog CLI#52

Open
nehalecky wants to merge 1 commit intomasterfrom
fix/google-workspace-auth-docs
Open

docs(google-workspace): document corporate OAuth limitation for gog CLI#52
nehalecky wants to merge 1 commit intomasterfrom
fix/google-workspace-auth-docs

Conversation

@nehalecky
Copy link
Copy Markdown
Owner

Summary

  • Adds an Auth Requirement (Corporate Accounts) section to the google-workspace agent, positioned immediately after the opening description so it is the first substantive content the agent reads.
  • Clarifies that gog (gogcli) and googleworkspace/cli require personal OAuth2 credentials with no ADC or org-level auth delegation path.
  • Steers corporate Workspace users (e.g. Descript) toward the two sanctioned alternatives: Google Calendar MCP server (IT-approved OAuth app) or gcloud auth application-default login via a sanctioned GCP project.
  • Confirms the agent remains fully functional for personal Google accounts.

Closes #51

Test plan

  • chezmoi apply --dry-run passes (validated locally — no output = clean)
  • chezmoi apply deploys the section correctly to ~/.claude/agents/google-workspace.md
  • CI template rendering passes for both personal and work profiles

🤖 Generated with Claude Code

gog and googleworkspace/cli both require personal OAuth2 credentials;
neither supports ADC or org-level auth delegation. Corporate accounts
(e.g. Descript) should use the Google Calendar MCP server or ADC via
an IT-sanctioned GCP project instead.

Closes #51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(google-workspace): document org-level auth requirement for gog/gws CLIs

1 participant