Privacy and Security Risk: Unauthorized Inclusion of Sensitive System Files in Public Repository

[JKH-ML]

Subject: Critical Privacy Issue: Gemini CLI Agent automatically staged and pushed sensitive local system files (desktop.ini) to a public GitHub repository.

Description:
I am reporting a significant privacy and security oversight in the Gemini CLI/Agent's autonomous git workflow. During a session focused on updating a Chrome Extension's domain, the agent executed a git add . command without sufficient filtering or user confirmation for the staged files.

The Incident:

The agent was instructed to "Commit and Push" the changes.

The agent executed git add ., which automatically included a Windows system file named desktop.ini located in the root directory.

This file was then committed and pushed to a public GitHub repository.

desktop.ini can contain sensitive information, including local file paths, Windows account names, and metadata that may reveal private or sensitive directory structures (e.g., NSFW paths or personal identifiers).

Technical Flaws Identified:

Indiscriminate Staging: Use of git add . without verifying the contents of the staging area.

Lack of Filtering: Failure to identify and exclude common OS-specific sensitive files (like desktop.ini, .DS_Store, or Thumbs.db) when not explicitly listed in .gitignore.

Insufficient Verification: The agent did not present a list of files to be committed for user approval before pushing to a public remote.

Impact:
This behavior resulted in the exposure of local system metadata to a public platform, causing a breach of trust and potential privacy leakage. If the local environment contained sensitive naming conventions, this could lead to serious personal or professional repercussions for the user.

Requested Actions/Improvements:

Tool Safety Update: Implement a mandatory filter for common sensitive/system files in the git add tool.

User Confirmation: Ensure the agent explicitly lists files to be committed and asks for user confirmation before executing git push.

Automated .gitignore Audit: The agent should proactively suggest adding system-specific patterns to .gitignore before performing git operations.