Skip to content

Conversation

@psinha40898
Copy link
Contributor

Summary

Currently pasting images creates a temporary directory inside the project which requires users to add that path to .gitignore
This PR has the temporary directory live inside ~/.gemini/tmp/${project_hash}/

It treats that path as valid in the workspace

Details

By deliberately adding this path as part of the "workspace" it should work as intended including for all sandbox modes

Related Issues

Fixes #15453

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

Moves clipboard image storage from the project root to  to keep the workspace clean.

- Update Storage to generate project-specific temporary paths.
- Register the clipboard directory in WorkspaceContext to ensure access in sandboxed environments.
- Refactor Config initialization to inject the clipboard path directly into the context.
- Update  to use absolute paths for pasted images.
@psinha40898 psinha40898 requested a review from a team as a code owner December 24, 2025 23:17
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @psinha40898, 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 refactors how temporary clipboard images are managed, moving them from a project-local .gemini-clipboard directory to a dedicated, project-specific temporary location under the user's home directory. This change resolves the inconvenience of having to add temporary files to .gitignore and ensures that these images are properly integrated into the application's workspace context for seamless operation.

Highlights

  • Clipboard Image Relocation: Temporary clipboard images are now stored in a project-specific directory within the user's home directory (~/.gemini/tmp/${project_hash}/clipboard) instead of directly inside the project folder.
  • Improved Workspace Integration: The new temporary clipboard directory is explicitly added to the workspace context, ensuring it's recognized and handled correctly by the application.
  • Reduced Project Clutter: This change eliminates the need for users to manually add .gemini-clipboard to their .gitignore files, simplifying project setup.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

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 refactors the handling of clipboard images by relocating the temporary directory from within the project folder to a project-specific directory in ~/.gemini/tmp/. This is a great improvement as it avoids the need for users to add this temporary path to their .gitignore. While the changes are generally good for security and workspace management, a high-severity command injection vulnerability was identified in the saveClipboardImage function on macOS. The file path is not properly sanitized before being used in an AppleScript command, which could allow for arbitrary code execution if a user operates in a maliciously named directory. Specific details and recommendations are provided in the review comments. Otherwise, the implementation is clean and effectively addresses the stated problem, with key changes including a new getProjectClipboardDir() method, earlier Storage service initialization, and updates to saveClipboardImage and cleanupOldClipboardImages utilities, all covered by updated tests.

Comment on lines 74 to 76
export async function saveClipboardImage(
targetDir?: string,
storage: Storage,
): Promise<string | null> {
Copy link
Contributor

Choose a reason for hiding this comment

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

security-high high

The saveClipboardImage function is vulnerable to command injection on macOS. The tempFilePath variable, which is derived from the project's root directory path (storage.getProjectClipboardDir()), is used to construct an AppleScript command without proper escaping. If a user runs the CLI in a directory with a specially crafted name containing double quotes, they can inject arbitrary AppleScript, which can in turn execute shell commands. For example, a directory named my\"project & do shell script \"touch /tmp/pwned\" would allow command execution.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not introduced in this PR

@psinha40898 psinha40898 marked this pull request as draft December 24, 2025 23:51
@psinha40898 psinha40898 marked this pull request as ready for review December 24, 2025 23:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

avoid creating project/.gemini-clipboard/

1 participant