Skip to content

Comments

chore: update folder trust error messaging#18402

Merged
galz10 merged 7 commits intomainfrom
galzahavi/add/untrusted-warning
Feb 5, 2026
Merged

chore: update folder trust error messaging#18402
galz10 merged 7 commits intomainfrom
galzahavi/add/untrusted-warning

Conversation

@galz10
Copy link
Collaborator

@galz10 galz10 commented Feb 5, 2026

Summary

Updates the folder trust warning message to clearly specify which features are restricted when a folder is untrusted.

Details

The previous message was vague ('Some features may be disabled'). The new message explicitly lists that project settings, hooks, MCPs, and GEMINI.md files will not be applied, providing better clarity to the user.

Related Issues

How to Validate

  1. Open the Gemini CLI in a directory that has not been explicitly trusted.
  2. Observe the initial information message.
  3. Verify the text reads: 'This folder is untrusted, project settings, hooks, mcps, and GEMINI.md files will not be applied for this folder. Use the /permissions command to change the trust level.'

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

@galz10 galz10 requested a review from a team as a code owner February 5, 2026 21:17
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @galz10, I'm Gemini Code Assist1! 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 enhances user clarity by refining the warning message displayed when a folder is untrusted within the Gemini CLI. The update provides specific details about which functionalities are restricted, ensuring users have a better understanding of the implications of an untrusted folder.

Highlights

  • Improved Folder Trust Warning: The warning message displayed when a folder is untrusted has been updated to explicitly list the features that will not be applied (project settings, hooks, MCPs, and GEMINI.md files), replacing a vague "Some features may be disabled" message.
Changelog
  • packages/cli/src/ui/hooks/useFolderTrust.ts
    • Updated the text property of the MessageType.INFO object to provide a more detailed explanation of features restricted in an untrusted folder.
Activity
  • The pull request author, galz10, has updated the folder trust error messaging.
  • The author has marked the "Added/updated tests" and "Validated on required platforms/methods: MacOS (npm run)" checklist items as complete.
  • No specific review comments or further activity are noted in the provided context.
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.

@github-actions
Copy link

github-actions bot commented Feb 5, 2026

Size Change: +54 B (0%)

Total Size: 23.7 MB

ℹ️ View Unchanged
Filename Size Change
./bundle/gemini.js 23.7 MB +54 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

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request improves the folder trust warning message by making it more specific, which enhances user clarity. This is a positive change. My review includes a minor suggestion to correct the capitalization of an acronym in the new message for better professionalism and consistency.

galz10 and others added 3 commits February 5, 2026 13:24
@gemini-cli gemini-cli bot added the status/need-issue Pull requests that need to have an associated issue. label Feb 5, 2026
@galz10 galz10 enabled auto-merge February 5, 2026 22:22
@galz10 galz10 disabled auto-merge February 5, 2026 22:36
@galz10 galz10 enabled auto-merge February 5, 2026 22:36
@galz10 galz10 added this pull request to the merge queue Feb 5, 2026
Merged via the queue into main with commit 83c6342 Feb 5, 2026
26 checks passed
@galz10 galz10 deleted the galzahavi/add/untrusted-warning branch February 5, 2026 23:34
sidwan02 pushed a commit to sidwan02/gemini-cli-gemma that referenced this pull request Feb 6, 2026
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
aswinashok44 pushed a commit to aswinashok44/gemini-cli that referenced this pull request Feb 9, 2026
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status/need-issue Pull requests that need to have an associated issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants