(docs) update sandboxing documentation#25930
Conversation
Summary of ChangesHello, 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 significantly enhances the sandboxing documentation for the Gemini CLI. By restructuring the content for better flow and adding detailed technical guidance on container-based workflows, the update aims to reduce user friction and clarify common configuration patterns for advanced sandboxing scenarios. Highlights
Using Gemini Code AssistThe 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
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 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. Footnotes
|
|
Size Change: -4 B (0%) Total Size: 33.7 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Code Review
This pull request updates the documentation for the Gemini CLI sandbox feature, adding a new quickstart guide, detailed configuration instructions, and advanced usage examples for Docker and file mounting. A correction was identified in the Docker run command example, where double backslashes were incorrectly used for line continuation in a bash context.
Note: Security Review has been skipped due to the limited scope of the PR.
|
I was reading the docs today and I think the The docs imply Anothe issue is that we cannot combine sandbox options in the config and If -s is present, it wins over my configuration, so {
"tools": {
"sandbox": {
"command": "sandbox-exec",
"allowedPaths": [...]
}
}
}I can file a separate issue but though it might get lost in the noise. |
Update sandbox documentation for Docker container workflows and other details
Summary
This PR expands and reorganizes the
docs/cli/sandbox.mddocumentation to provide clearer, more sequential instructions for users utilizing container-based (Docker/Podman) sandboxing. It addresses common user questions regarding workspace path resolution, custom image configuration (such as Artifact Registry), and nested Docker setups.Resolves #25929
Changes
settings.jsonand theGEMINI_SANDBOX_IMAGEenvironment variable..gemini/sandbox.Dockerfileand theBUILD_SANDBOX=1environment variable.SANDBOX_MOUNTSenvironment variable to mount additional files or directories outside the project workspace into the sandbox.npm run formatto ensure adherence to Markdown and Prettier guidelines.Validation
npm run formatsuccessfully passed.