Skip to content

Update README.md#106

Closed
mquirosbloch wants to merge 1 commit intomainfrom
mquirosbloch-patch-1
Closed

Update README.md#106
mquirosbloch wants to merge 1 commit intomainfrom
mquirosbloch-patch-1

Conversation

@mquirosbloch
Copy link
Collaborator

No description provided.

@google-cla
Copy link

google-cla bot commented Jan 29, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@mquirosbloch mquirosbloch requested a review from wt17 January 29, 2026 23:51
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @mquirosbloch, 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 enhances the clarity of the README.md file by refining the documentation for available models. The changes aim to provide users with a more precise understanding of which models are accessible via the Gemini Developer API and Vertex AI Client, and which are exclusive to the Gemini Developer API, thereby improving the user experience when selecting a model.

Highlights

  • Model Availability Clarification: The README.md has been updated to clearly distinguish which models are available across different platforms (Gemini Developer API and Vertex AI Client vs. Gemini Developer API only).
  • Documentation Improvement: The documentation now provides better guidance on model selection by categorizing available models based on their supported APIs.
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

The pull request updates the README.md to clarify which models are available for the Gemini Developer API and Vertex AI. This is a good documentation improvement. My review includes one comment that points out an inconsistency between this new documentation and the code's behavior, suggesting a follow-up to add validation logic for a better user experience.

Comment on lines +122 to 129
You can choose the model to use by specifying the ```--model <model name>``` flag. Available options on Gemini Developer API and Vertex AI Client:

- `gemini-2.5-computer-use-preview-10-2025`: This is the default model.

Available options on Gemini Developer API only:

- `gemini-3-flash-preview`: The preview version of Gemini 3 Flash.
- `gemini-3-pro-preview`: The preview version of Gemini 3 Pro.
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

This is a helpful clarification in the documentation. However, it highlights an inconsistency with the current implementation in main.py. The code doesn't prevent a user from selecting a model that is incompatible with their chosen client (e.g., selecting a Gemini Developer API-only model while using the Vertex AI client). This will lead to a runtime error instead of a graceful failure with a clear error message.

To improve the user experience, I recommend adding validation in main.py to check for compatible model and client combinations. This would provide an immediate and clear error to the user if they make an invalid selection. This can be addressed in a follow-up.

@wt17 wt17 closed this Jan 30, 2026
@wt17 wt17 deleted the mquirosbloch-patch-1 branch January 30, 2026 06:31

**Available Models:**

You can choose the model to use by specifying the ```--model <model name>``` flag. Available options:

Choose a reason for hiding this comment

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

Motorola Edge 60pro

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.

3 participants