Split and add Notebooks to Gemini Robotics by xpfgg · Pull Request #1138 · google-gemini/cookbook

xpfgg · 2026-02-12T16:46:49Z

No description provided.

review-notebook-app · 2026-02-12T16:46:55Z

Check out this pull request on

See visual diffs & provide feedback on Jupyter Notebooks.

Powered by ReviewNB

gemini-code-assist · 2026-02-12T17:02:29Z

Summary of Changes

Hello @xpfgg, 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 the existing Gemini Robotics content by moving it into a dedicated subdirectory and expanding it with new, detailed notebooks. The primary goal is to provide a more structured and comprehensive learning path for users interested in applying Gemini API features to robotics, focusing on determinism, latency control, and precise action.

Highlights

Notebook Restructuring: The Gemini Robotics-ER 1.5 notebook has been moved into a dedicated gemini_robotics subdirectory for better organization.
New Robotics Documentation: A new README.md file was added within the gemini_robotics directory, providing an overview and recommended order for the new robotics-focused notebooks.
New API Features Notebook: A new Jupyter notebook, robotics_api_features.ipynb, was introduced to demonstrate key Gemini API features essential for robotics, such as JSON mode, thinking budgets, and code execution.

Changelog

README.md
- Updated the link for the Gemini Robotics-ER 1.5 notebook to reflect its new location.
quickstarts/gemini_robotics/README.md
- Added a new README file to introduce the Gemini for Robotics notebook series and outline the recommended learning path.
quickstarts/gemini_robotics/robotics_api_features.ipynb
- Added a new Jupyter notebook demonstrating how to use Gemini API features like JSON mode, thinking budgets, and code execution for robust robotics applications.

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.

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 effectively splits the robotics notebook into a more organized structure with a dedicated directory and README. The new robotics_api_features.ipynb notebook is a good addition. My review focuses on several areas for improvement in the new files to align with the repository's style guide and best practices. Specifically, I've pointed out a critical issue with an external dependency on a personal repository, and several medium-severity issues related to missing Colab badges, hardcoded model IDs, and inconsistent language use ('we' vs. 'you') as per the style guide. Addressing these will improve the quality, maintainability, and security of the new content.

gemini-code-assist · 2026-02-12T17:04:09Z

quickstarts/gemini_robotics/robotics_api_features.ipynb

+        "from PIL import Image\n",
+        "\n",
+        "if not os.path.exists('robotics_utils.py'):\n",
+        "    url = \"https://raw.githubusercontent.com/williamito/robotics-samples/refs/heads/main/robotics_utils.py\"\n",


This notebook downloads a utility script from a personal GitHub repository (williamito/robotics-samples). For security and maintainability, official cookbook examples must not depend on personal or unofficial repositories. Please vendor the robotics_utils.py script into this repository or another official Google-owned repository and update the URL.

gemini-code-assist · 2026-02-12T17:04:09Z

quickstarts/gemini_robotics/README.md

+
+## Notebooks
+
+We recommend going through the notebooks in the following order:


According to the repository style guide (line 91), documentation should use the second person ('you') instead of 'we'. Please rephrase this sentence to avoid using 'we'. For example: 'The notebooks should be reviewed in the following order:'.

References

Use second person: "you" rather than "we". You will fail the lint check otherwise. ^(link)

gemini-code-assist · 2026-02-12T17:04:09Z

quickstarts/gemini_robotics/robotics_api_features.ipynb

+    {
+      "cell_type": "markdown",
+      "metadata": {
+        "id": "CZC64QGBZ2v9"
+      },
+      "source": [
+        "# Engineering Reliability (API Features)"
+      ]
+    },


According to the repository style guide (line 50), an 'Open in Colab' badge should be included in a new markdown cell immediately after the H1 title cell. This allows users to easily open the notebook in Colab.

The URL for the badge should be https://colab.research.google.com/github/google-gemini/cookbook/blob/main/quickstarts/gemini_robotics/robotics_api_features.ipynb.

References

Include the "open in colab" button immediately after the H1. It should look like <a target=\"_blank\" href=\"URL\"><img src=\"https://colab.research.google.com/assets/colab-badge.svg\" height=30/> where URL should be https://colab.research.google.com/github/google-gemini/cookbook/blob/main/ followed by the notebook location in the cookbook. ^(link)

gemini-code-assist · 2026-02-12T17:04:09Z

quickstarts/gemini_robotics/robotics_api_features.ipynb

+      },
+      "outputs": [],
+      "source": [
+        "%pip install -U -q google-genai google-colab"


The style guide (line 25) specifies that the google-genai package should be installed with a minimum version to ensure compatibility and prevent issues with older versions.

Suggested change

"%pip install -U -q google-genai google-colab"

"%pip install -U -q 'google-genai>=1.0.0' google-colab"

References

%pip install -U -q 'google-genai>=1.0.0' is the right way to install the SDK. The version indicated should reflect the minimum version needed to use the features used in the notebook (1.0.0 by default or in doubt). ^(link)

gemini-code-assist · 2026-02-12T17:04:10Z

quickstarts/gemini_robotics/robotics_api_features.ipynb

+        "\n",
+        "GOOGLE_API_KEY = userdata.get(\"GOOGLE_API_KEY\")\n",
+        "client = genai.Client(api_key=GOOGLE_API_KEY)\n",
+        "MODEL_ID = \"gemini-3-flash-preview\""


The style guide (line 72) recommends using a Colab form element for model selection to improve maintainability and allow users to easily experiment. Since this notebook has specific model requirements for the 'Thinking' feature, using a simple input field is appropriate.

MODEL_ID = "gemini-3-flash-preview" # @param {type:"string"}

References

When selecting a model, use a colab selector for easier maintainability. ^(link)

gemini-code-assist · 2026-02-12T17:04:10Z

quickstarts/gemini_robotics/robotics_api_features.ipynb

+      },
+      "source": [
+        "### Example: Eliminating Filler Text\n",
+        "By enforcing JSON mode, we create a strict contract between the AI and our robot controller, ensuring the output is always machine-readable."


The style guide (line 91) recommends using the second person ('you') instead of 'we' to maintain a consistent voice across all documentation.

"By enforcing JSON mode, you create a strict contract between the AI and your robot controller, ensuring the output is always machine-readable."

References

Use second person: "you" rather than "we". You will fail the lint check otherwise. ^(link)

xpfgg added 2 commits February 12, 2026 16:39

Split and clarify Robotics Notebooks

5772ca9

Remove empty cells and broken links

555fa82

github-actions bot added status:awaiting review PR awaiting review from a maintainer component:quickstarts Issues/PR referencing quickstarts folder labels Feb 12, 2026

gemini-code-assist bot reviewed Feb 12, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Split and add Notebooks to Gemini Robotics#1138

Split and add Notebooks to Gemini Robotics#1138
xpfgg wants to merge 2 commits intogoogle-gemini:mainfrom
xpfgg:main

xpfgg commented Feb 12, 2026

Uh oh!

review-notebook-app bot commented Feb 12, 2026

Uh oh!

gemini-code-assist bot commented Feb 12, 2026

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Feb 12, 2026

Uh oh!

gemini-code-assist bot Feb 12, 2026

Uh oh!

gemini-code-assist bot Feb 12, 2026

Uh oh!

gemini-code-assist bot Feb 12, 2026

Uh oh!

gemini-code-assist bot Feb 12, 2026

Uh oh!

gemini-code-assist bot Feb 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant


		## Notebooks

		We recommend going through the notebooks in the following order:

	"%pip install -U -q google-genai google-colab"
	"%pip install -U -q 'google-genai>=1.0.0' google-colab"

Conversation

xpfgg commented Feb 12, 2026

Uh oh!

review-notebook-app bot commented Feb 12, 2026

Uh oh!

gemini-code-assist bot commented Feb 12, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant