feat(settings): rename negative settings to positive naming (disable* -> enable*)

[afarber]

Summary

Standardize boolean toggle settings to use positive "Enable X" naming instead of "Disable X" to avoid double negatives and improve UX consistency. Adds automatic migration for existing user configurations.

Details

Old Setting	New Setting	Default
general.disableAutoUpdate	general.enableAutoUpdate	true
general.disableUpdateNag	general.enableAutoUpdateNotification	true
context.fileFiltering.disableFuzzySearch	context.fileFiltering.enableFuzzySearch	true
ui.accessibility.disableLoadingPhrases	ui.accessibility.enableLoadingPhrases	true

Migration logic in migrateDeprecatedSettings() automatically converts old settings with inverted values. Old configs like disableAutoUpdate: true become enableAutoUpdate: false.

Also renamed internal parameter isAutoUpdateDisabled to isAutoUpdateEnabled in installationInfo.ts for consistent positive boolean logic throughout the codebase.

Note: security.disableYoloMode intentionally kept as-is since "disable" framing is appropriate for a dangerous mode.

Related Issues

Fixes #14035, #15013, #13380, and partially #15237

How to Validate

1. Fresh install: Run gemini and verify settings dialog shows "Enable Auto Update Notification", "Enable Loading Phrases", etc.
2. Migration test: Create ~/.gemini/settings.json with old format:

{
  "general": {
    "disableAutoUpdate": true,
    "disableUpdateNag": true
  },
  "ui": {
    "accessibility": {
      "disableLoadingPhrases": true
    }
  },
  "context": {
    "fileFiltering": {
      "disableFuzzySearch": true
    }
  },
  "security": {
    "disableYoloMode": true
  }
}

3. Run gemini, then check settings - should show:
   - "Enable Auto Update" as OFF
   - "Enable Update Prompts" as OFF
   - "Enable Loading Phrases" as OFF
   - "Enable Fuzzy Search" as OFF
   - "Disable YOLO Mode" as ON (unchanged, kept as-is)
4. Run npm run preflight - all tests pass

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 @afarber, 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 refactors several boolean configuration settings to enhance user experience and consistency. By standardizing naming conventions from 'disableX' to 'enableX' and inverting their default values, the system avoids confusing double negatives. Crucially, it includes robust migration logic to ensure that existing user settings are automatically updated without data loss or manual intervention, making the transition transparent for users.

Highlights

• Setting Renaming for Consistency: Four boolean settings have been renamed from a 'disableX' format to an 'enableX' format to improve UX consistency and avoid double negatives. These include general.disableAutoUpdate to general.enableAutoUpdate, general.disableUpdateNag to general.enableUpdatePrompts, context.fileFiltering.disableFuzzySearch to context.fileFiltering.enableFuzzySearch, and ui.accessibility.disableLoadingPhrases to ui.accessibility.enableLoadingPhrases.
• Inverted Default Values: Along with the renaming, the default values for these settings have been inverted. For example, general.enableAutoUpdate now defaults to true (whereas disableAutoUpdate defaulted to false).
• Automatic Migration Logic: Automatic migration logic has been implemented in migrateDeprecatedSettings() to seamlessly convert existing user configurations. If an old setting like disableAutoUpdate: true is found, it will be automatically converted to enableAutoUpdate: false.
• Documentation and Test Updates: All relevant documentation, settings schemas, and test files have been updated to reflect the new setting names, their inverted logic, and the migration process.

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 standardizes boolean toggle settings to use positive "Enable X" naming, which is a great improvement for UX consistency. The changes are extensive, touching documentation, configuration schemas, tests, and UI components. The inclusion of automatic migration logic for existing user configurations is well-implemented. My main feedback is a suggestion to refactor the migration logic for general settings to be more efficient and maintainable by combining multiple file writes into one.

[afarber]

/gemini review

[gemini-code-assist]

Code Review

This pull request is a great step towards standardizing boolean toggle settings to use positive naming, which improves consistency and user experience. The automatic migration for existing user configurations is a thoughtful addition. The changes are comprehensive, covering documentation, configuration, tests, and UI components. I've identified one area for improvement in the migration logic to make it more robust for future changes.

[devr0306]

Great job on this! A few comments but otherwise mostly looks good. A PR recently got merged which enables defaults on settings so some of the ?? could be removed too.

[devr0306]

lgtm

[jacob314]

Thanks for adding this! To unblock some work I'll make a couple tweaks on top of this PR so we can land it today.

[g-samroberts]

LGTM for docs.

[jacob314]

[Chubong630]

Subject: Confirmation of Merge for Pull Request #14142 Dear Jacob, Thank you for the update. I would like to confirm that the merge of pull request #14142 has been completed successfully. Should there be any further actions required or if you need additional information, please feel free to reach out. Best regards, [Your Name] [Your Position] [Your Contact Information] Vào Thứ 7, 17 thg 1, 2026 vào lúc 05:43 Jacob Richman < ***@***.***> đã viết:

…

Merged #14142 <#14142> into main. — Reply to this email directly, view it on GitHub <#14142 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BTW7LWWXXEKPXPWBTG3Q4734HFSRZAVCNFSM6AAAAACNREAJYWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRSGEYDMOBZGMYTSMA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>