Enable extension config by default

[chrstnb]

Summary

We're launching this next week!

Details

Related Issues

How to Validate

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[gemini-code-assist]

Summary of Changes

Hello @chrstnb, 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 transitions the experimental.extensionConfig feature to be enabled by default. This change streamlines the user experience by automatically activating the functionality for requesting and fetching extension settings, aligning with an upcoming launch.

Highlights

• Default Extension Configuration: The experimental.extensionConfig setting is now enabled by default, allowing requesting and fetching of extension settings without manual configuration.
• Documentation Update: The documentation for experimental.extensionConfig has been updated to reflect its new default value of true.
• Schema Updates: Both the internal TypeScript settings schema and the public JSON settings schema have been updated to set the default for experimental.extensionConfig to true.

Changelog

• docs/get-started/configuration.md
  • Updated the default value for experimental.extensionConfig from false to true in the configuration documentation.
• packages/cli/src/config/settingsSchema.ts
  • Changed the default property for experimental.extensionConfig from false to true within the internal settings schema.
• schemas/settings.schema.json
  • Modified the default property and markdownDescription for extensionConfig to reflect the new default value of true in the JSON schema.

Activity

• The author noted that the feature is scheduled for launch next week, indicating a time-sensitive change.

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 enables the extensionConfig feature by default across the configuration files. This is a good step towards launching the feature. My review includes a suggestion to move this setting out of the experimental category to better reflect its new stable status, which will improve the configuration structure and maintainability. This comment aligns with general best practices for code organization and feature lifecycle management, and does not contradict any of the provided rules.

[github-actions]

Size Change: -3 B (0%)

Total Size: 23.8 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	23.8 MB	-3 B (0%)
./bundle/sandbox-macos-permissive-closed.sb	1.03 kB	0 B
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-closed.sb	3.29 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B

_{compressed-size-action}

[chrstnb]

/patch preview

[github-actions]

✅ Patch workflow(s) dispatched successfully!

📋 Details:

• Channels: preview
• Commit: d86b1f7b7edf7a78977826edac96537b55bfe009
• Workflows Created: 1

🔗 Track Progress:

• View patch workflows
• This workflow run

[github-actions]

🚀 Patch PR Created!

📋 Patch Details:

• Environment: prod
• Channel: preview → will publish to npm tag preview
• Commit: d86b1f7b7edf7a78977826edac96537b55bfe009
• Hotfix Branch: hotfix/v0.28.0-preview.2/0.28.0-preview.3/preview/cherry-pick-d86b1f7/pr-18447
• Hotfix PR: #18450

📝 Next Steps:

1. Review and approve the hotfix PR: #18450
2. Once merged, the patch release will automatically trigger
3. You'll receive updates here when the release completes

🔗 Track Progress:

• View hotfix PR #18450

[github-actions]

🚀 Patch Release Started!

📋 Release Details:

• Environment: prod
• Channel: preview → publishing to npm tag preview
• Version: v0.28.0-preview.2
• Hotfix PR: Merged ✅
• Release Branch: release/v0.28.0-preview.2-pr-18447

⏳ Status: The patch release is now running. You'll receive another update when it completes.

🔗 Track Progress:

• View release workflow

[github-actions]

✅ Patch Release Complete!

📦 Release Details:

• Version: 0.28.0-preview.3
• NPM Tag: preview
• Channel: preview
• Dry Run: false

🎉 Status: Your patch has been successfully released and published to npm!

📝 What's Available:

• GitHub Release: View release v0.28.0-preview.3
• NPM Package: npm install @google/gemini-cli@preview

🔗 Links:

• GitHub Release
• Workflow Run