Add interactions notebook.

[MarkDaoust]

No description provided.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[gemini-code-assist]

Summary of Changes

Hello @MarkDaoust, 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 introduces a new, extensive Jupyter notebook designed to serve as a quickstart guide for interacting with the Gemini API. The notebook provides practical, hands-on examples covering a wide array of functionalities, from basic text prompts to complex multimodal inputs and advanced agentic capabilities like function calling, code execution, and deep research. Its purpose is to enable developers to rapidly understand and implement various Gemini API features, fostering efficient integration and exploration of the model's diverse interaction paradigms.

Highlights

• Introduction of a new Jupyter notebook: A comprehensive Get_started_Interactions.ipynb notebook has been added to guide users through various Gemini API interaction capabilities.
• Multimodal Interaction Demonstrations: The notebook includes examples for handling diverse input types such as text, images, PDF documents, audio, video, and YouTube links.
• Advanced API Features: Demonstrations cover system instructions, generation configuration, multi-turn chat management (including branching and manual history), structured JSON output using Pydantic, function calling, code execution, Google Search integration, and URL context processing.
• Asynchronous and Streaming Interactions: Examples for both streaming responses and asynchronous API requests are provided, showcasing flexible interaction patterns.

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. ↩

[gemini-code-assist]

Code Review

This pull request adds a new notebook, Get_started_Interactions.ipynb, which serves as a quickstart guide for the Gemini API interactions. The notebook is comprehensive, covering a wide range of features from standard text prompts to advanced functionalities like function calling, code execution, and multimodal inputs. However, there are several areas that need improvement to align with the repository's style guide and best practices. Specifically, the Colab badge URL is incorrect, the SDK installation command is not following the prescribed format, and the model selection should be implemented as a dropdown for better maintainability. Additionally, the notebook lacks saved outputs, which is a deviation from the ideal state described in the style guide.

[gemini-code-assist]

The 'Open in Colab' badge points to Get_started.ipynb instead of the correct Get_started_Interactions.ipynb. Please update the URL to ensure users are directed to the correct notebook.

<a target="_blank" href="https://colab.research.google.com/github/google-gemini/cookbook/blob/main/quickstarts/Get_started_Interactions.ipynb"><img src="https://colab.research.google.com/assets/colab-badge.svg" height=30/></a>

[gemini-code-assist]

The notebook title is 'Gemini API: Getting started with Gemini models', but this notebook seems to be about the Interactions API specifically. It would be clearer to update the title to reflect this, for example: '# Gemini API: Get started with Interactions'.

[gemini-code-assist]

According to the style guide (line 55), you should use %pip instead of !pip3. Also, the package name should be google-genai and it's recommended to use the -U flag for upgrades.

%pip install -U -q 'google-genai>=1.55.0'

References

1. The style guide specifies using %pip instead of !pip for installing packages in notebooks. ^(link)
2. The style guide specifies that the correct way to install the SDK is with %pip install -U -q 'google-genai>=1.0.0'. ^(link)

[gemini-code-assist]

This helper function is quite long and contains a lot of logic for displaying different output types. According to the style guide (line 60), such necessary but uninteresting code should be hidden in a toggleable code cell by adding # @title as the first line. This improves the notebook's readability by allowing users to focus on the core examples.

# @title Utility functions
from IPython.display import Audio,Markdown, Image, display
import textwrap
import base64
import wave


def wave_file(filename, pcm, channels=1, rate=24000, sample_width=2):
   with wave.open(str(filename), "wb") as wf:
      wf.setnchannels(channels)
      wf.setsampwidth(sample_width)
      wf.setframerate(rate)
      wf.writeframes(pcm)


import collections


def show_outputs(outputs):
  for part in outputs:
    if part.type == 'text':
      display(Markdown(part.text))
    elif part.type == 'thought':
      pass
    elif part.type == 'image':
      display(Image(data=base64.b64decode(part.data)))
    elif part.type == 'function_call':
      print(repr(part))
    elif part.type == 'audio':
      audio_data = part.data
      wave_file("speech.wav", base64.b64decode(audio_data))
      display(Audio("speech.wav"))
    elif part.type == 'code_execution_call':
      display(Markdown(f"\n```python\n{part.arguments.code}\n```\n"))
    elif part.type == 'code_execution_result':
      display(Markdown(part.result.join(['\n```\n', '\n```\n'])))
    elif part.type == 'google_search_call':
      if part.arguments is None:
        display(Markdown(f"\n```\ngogle_search(???)\n```\n"))
      else:
        display(Markdown(f"\n```\ngogle_search({part.arguments.queries})\n```\n"))

    elif part.type == 'google_search_result':
      links = []
      for result in part.result:
        links.append(f"* [{result.title}]({result.url})")
      display(Markdown("\n".join(links)))
    elif part.type == 'url_context_call':
      display(Markdown("Url Context"))
    elif part.type == 'url_context_result':
      markdown_lines = []
      status_emoji = {"SUCCESS": "✅", "FAIL": "❌"}
      for item in part.result:
          emoji = status_emoji.get(item.status, "❓") # Default to '❓' if status is unknown
          line = f"* {emoji} [{item.url}]({item.url})"
          markdown_lines.append(line)

      display(Markdown("\n".join(markdown_lines)))

References

1. The style guide recommends hiding necessary but uninteresting code (like helper functions) in a toggleable code cell by putting # @title as the first line. ^(link)

[gemini-code-assist]

The style guide (line 72) recommends using a Colab form for model selection to improve maintainability. This allows users to easily switch between different models without editing the code.

MODEL_ID = "gemini-2.5-flash"  # @param ["gemini-2.5-flash-lite", "gemini-2.5-flash", "gemini-2.5-pro", "gemini-3-flash-preview", "gemini-3-pro-preview"] {"allow-input":true, "isTemplate": true}

References

1. The style guide suggests using a Colab selector for model selection for easier maintainability. ^(link)

[gemini-code-assist]

This notebook is missing the outputs for the code cells. According to the style guide (lines 41-42), it's ideal to have outputs saved so users can see what the code does without running it. Please run the notebook and save the outputs before merging.

References

1. The style guide indicates that ideally, outputs should be saved in notebooks so that one can see what the code does without running it. ^(link)