Add documentation for using Gemini 3.1 Pro Preview#428
Add documentation for using Gemini 3.1 Pro Preview#428IshitaSingh07 wants to merge 1 commit intoBeehiveInnovations:mainfrom
Conversation
Added instructions for using Gemini 3.1 Pro Preview API.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the README to include instructions for Gemini 3.1 Pro Preview. Feedback identifies a syntax error in a code block, a version mismatch between the documentation and configuration files, and the accidental removal of important general provider information. Additionally, some content mentioned in the PR description is missing and header levels require correction.
| 2. **Set your API Key** | ||
| Add it to your environment variables or `.env` file: | ||
| ```bash | ||
| GEMINI_API_KEY=your_api_key_here |
There was a problem hiding this comment.
The bash code block starting on line 215 is missing its closing triple backticks. This will cause the subsequent sections of the README to be rendered incorrectly as part of the code block.
| ## Provider Configuration | ||
|
|
||
| PAL activates any provider that has credentials in your `.env`. See `.env.example` for deeper customization. | ||
| ## Using Gemini 3.1 Pro Preview |
There was a problem hiding this comment.
Version mismatch: This section refers to Gemini 3.1, but the configuration file conf/gemini_models.json (line 30) defines the model as Gemini 3.0 (gemini-3-pro-preview). Please ensure the documentation matches the actual model configuration.
|
|
||
| PAL MCP supports Gemini models through Google's Generative AI API. You can use newer models such as **Gemini 3.1 Pro Preview** if they are available in your API access. | ||
|
|
||
| ### Steps to Use Gemini 3.1 Pro Preview |
There was a problem hiding this comment.
The PR description mentions adding 'fallback guidance' and 'Configure the model' instructions, but these are missing from the changes. Additionally, the new section uses a level 2 header (##) instead of level 3 (###), and the general provider activation note was removed and should be restored.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: deaaab47b4
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| ```bash | ||
| GEMINI_API_KEY=your_api_key_here | ||
| ## Core Tools |
There was a problem hiding this comment.
The new Gemini setup section opens a fenced block with bash but never closes it, so in Markdown renderers (including GitHub) everything from `## Core Tools` onward is treated as code. This breaks the README structure and makes major sections/anchors unreadable for all users following the docs; add the missing closing after GEMINI_API_KEY=... (and then continue the numbered steps outside the fence).
Useful? React with 👍 / 👎.
1 participant
Description
This PR adds documentation explaining how to use Gemini 3.1 Pro Preview with PAL MCP.
Changes
Why this change?
The current documentation does not clarify whether newer Gemini models like Gemini 3.1 Pro Preview can be used. This update helps new users understand how to configure and use it properly.
Issue
Closes