Fix Gemini extension installation issue and update docs

[jpoehnelt]

Fixes an issue where prompting for sensitive values during the Gemini extension installation triggered a keychain availability error. The gws CLI securely handles its own authentication via standard environments.
This also updates the README and CONTEXT documentation to provide instructions and rules for agents.

---

PR created automatically by Jules for task 17987082047493462031 started by @jpoehnelt

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[changeset-bot]

🦋 Changeset detected

Latest commit: 807f184

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@googleworkspace/cli	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical installation issue for the Gemini extension by streamlining its authentication configuration, ensuring smoother setup. Concurrently, it significantly enhances the documentation for AI agents, providing clear guidelines on how to interact with Google Workspace APIs via gws effectively and safely, thereby improving agent autonomy and preventing common pitfalls.

Highlights

• Gemini Extension Installation Fix: Resolved a Gemini extension installation problem by removing redundant authentication settings from gemini-extension.json, which previously caused keychain availability errors during sensitive value prompts.
• Agent Rules of Engagement: Introduced a new "Rules of Engagement for Agents" section in CONTEXT.md to guide AI agents on best practices for using gws commands, covering schema discovery, context window protection, and dry-run safety.
• Gemini CLI Extension Documentation: Added a comprehensive "Gemini CLI Extension" section to README.md, detailing installation steps and optimization strategies for integrating gws with the Gemini CLI.

Changelog

• .changeset/gemini-extension-update.md
  • Added a new changeset file documenting the fix for the Gemini extension installation and documentation updates.
• CONTEXT.md
  • Added a new section titled "Rules of Engagement for Agents" with guidelines for schema discovery, context window protection, and dry-run safety.
• README.md
  • Introduced a new "Gemini CLI Extension" section, including installation instructions and advice on optimizing gws for Gemini CLI agents.
• gemini-extension.json
  • Removed several authentication-related settings (Credentials File, OAuth Client ID, OAuth Client Secret, Impersonated User) from the extension configuration.

Activity

• The pull request was automatically created by Jules for task 17987082047493462031, initiated by @jpoehnelt.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request successfully addresses an installation issue with the Gemini extension by removing unnecessary authentication settings from gemini-extension.json and delegating authentication to the gws CLI itself. The accompanying documentation updates in README.md and CONTEXT.md provide clear instructions and rules for agent-based usage. The changes are logical and well-executed. I have one suggestion to enhance the clarity of the README.md to prevent potential user confusion.

_{Note: Security Review has been skipped due to the limited scope of the PR.}