Skip to content

Gemini 3.1 pro#2194

Closed
aarondr77 wants to merge 12 commits intodevfrom
gemini-3.1-por
Closed

Gemini 3.1 pro#2194
aarondr77 wants to merge 12 commits intodevfrom
gemini-3.1-por

Conversation

@aarondr77
Copy link
Member

@aarondr77 aarondr77 commented Feb 27, 2026

Description

Gemini 3.1 Pro!

Testing

Try it out


Note

Medium Risk
Removes the agent execution depth limit in the JupyterLab extension, which could allow longer-running or stuck agent loops until explicitly stopped. Other changes are mostly prompt/content and model-name updates with low functional risk.

Overview
Adds Gemini 3.1 Pro support end-to-end by replacing gemini-3-pro-preview with gemini-3.1-pro-preview in backend model lists/order (model_utils.py), frontend model constants (models.ts), and associated tests.

Enhances agent prompting for Excel conversions by introducing EXCEL_TO_PYTHON_RULES (new excel_to_python_rules.py) and injecting it into the agent system message via prompt_constants.py/agent_system_message.py.

Changes agent runtime behavior by removing the AGENT_EXECUTION_DEPTH_LIMIT in useAgentExecution.ts, so executions no longer auto-stop with a “review and continue” message after a fixed number of steps.

Written by Cursor Bugbot for commit b873a83. This will update automatically on new commits. Configure here.

@vercel
Copy link

vercel bot commented Feb 27, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
monorepo Ready Ready Preview, Comment Feb 27, 2026 3:49pm

Request Review

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.


// Loop through each message in the plan and send it to the AI
while (!isAgentFinished && agentExecutionDepth <= AGENT_EXECUTION_DEPTH_LIMIT) {
while (!isAgentFinished) {
Copy link

Choose a reason for hiding this comment

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

Removing agent depth limit risks unbounded execution loop

Medium Severity

The AGENT_EXECUTION_DEPTH_LIMIT constant (previously 20) and its guard in the while loop have been completely removed, leaving while (!isAgentFinished) with no upper bound. If the LLM never returns a finished_task response — due to a model error, looping behavior, or the new Excel-to-Python workflow getting stuck — the agent will make unbounded API calls and run code cells indefinitely with no automatic safety net. Only a manual user stop via shouldContinueAgentExecution can break the loop in that scenario.

Fix in Cursor Fix in Web

@aarondr77 aarondr77 closed this Mar 2, 2026
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.

2 participants