Skip to content

Add documentation for using Gemini 3.1 Pro Preview #428

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
IshitaSingh07 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add documentation for using Gemini 3.1 Pro Preview #428

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -200,8 +200,20 @@ cd pal-mcp-server

## Provider Configuration

PAL activates any provider that has credentials in your `.env`. See `.env.example` for deeper customization.
## Using Gemini 3.1 Pro Preview
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot Apr 7, 2026

Choose a reason for hiding this comment

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

medium

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
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot Apr 7, 2026

Choose a reason for hiding this comment

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

medium

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.


1. **Get a Gemini API Key**
- Visit: https://makersuite.google.com/app/apikey
- Generate your API key

2. **Set your API Key**
Add it to your environment variables or `.env` file:
```bash
GEMINI_API_KEY=your_api_key_here
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot Apr 7, 2026

Choose a reason for hiding this comment

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

high

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.

## Core Tools
Comment on lines +215 to 217
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot Apr 7, 2026

Choose a reason for hiding this comment

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

P2 Badge Close fenced code block in Gemini setup docs

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 👍 / 👎.


> **Note:** Each tool comes with its own multi-step workflow, parameters, and descriptions that consume valuable context window space even when not in use. To optimize performance, some tools are disabled by default. See [Tool Configuration](#tool-configuration) below to enable them.
Expand Down
Loading