Skip to content

Change default compress threshold to 0.5 for api key users#13517

Merged
jacob314 merged 1 commit intomainfrom
tomm_compress
Nov 20, 2025
Merged

Change default compress threshold to 0.5 for api key users#13517
jacob314 merged 1 commit intomainfrom
tomm_compress

Conversation

@scidomino
Copy link
Copy Markdown
Collaborator

@scidomino scidomino commented Nov 20, 2025

Summary

Changes the default compress threshold to 0.5 from 0.7.

Details

This adjusts the default compression threshold for api key users to 0.5.

Based on #13079

How to Validate

Start up and check the default in the settings screen.

Pre-Merge Checklist

  • Updated relevant documentation and README (if needed)
  • Added/updated tests (if needed)
  • Noted breaking changes (if any)
  • Validated on required platforms/methods:
    • MacOS
      • npm run
      • npx
      • Docker
      • Podman
      • Seatbelt
    • Windows
      • npm run
      • npx
      • Docker
    • Linux
      • npm run
      • npx
      • Docker

@scidomino scidomino requested a review from a team as a code owner November 20, 2025 17:14
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @scidomino, 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 adjusts the default context compression threshold to 0.5 from 0.7. This modification aims to proactively trigger context compression earlier, potentially leading to more efficient token usage and improved performance for API key users by reducing the amount of conversational history sent to the model.

Highlights

  • Default Compression Threshold: The default value for the model.compressionThreshold setting has been updated from 0.7 to 0.5. This change makes context compression more aggressive by default, triggering it earlier.
  • Configuration Consistency: The updated default value is consistently applied across the documentation, the CLI's internal settings schema, the core service constant, and the main settings JSON schema.
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
Copy Markdown
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

This pull request changes the default compression threshold from 0.7 to 0.5. The change is applied consistently across the codebase, documentation, and configuration schemas. However, a unit test that relies on the old default value has not been updated, which will likely cause it to fail. I've left a comment with details on how to fix the test.

Comment thread packages/core/src/services/chatCompressionService.ts
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Nov 20, 2025

Size Change: -2 B (0%)

Total Size: 21.1 MB

ℹ️ View Unchanged
Filename Size Change
./bundle/gemini.js 21.1 MB -2 B (0%)
./bundle/sandbox-macos-permissive-closed.sb 1.03 kB 0 B
./bundle/sandbox-macos-permissive-open.sb 890 B 0 B
./bundle/sandbox-macos-permissive-proxied.sb 1.31 kB 0 B
./bundle/sandbox-macos-restrictive-closed.sb 3.29 kB 0 B
./bundle/sandbox-macos-restrictive-open.sb 3.36 kB 0 B
./bundle/sandbox-macos-restrictive-proxied.sb 3.56 kB 0 B

compressed-size-action

Copy link
Copy Markdown
Member

@richieforeman richieforeman left a comment

Choose a reason for hiding this comment

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

LG

@scidomino scidomino enabled auto-merge November 20, 2025 18:36
label: 'Compression Threshold',
category: 'Model',
requiresRestart: true,
default: 0.7 as number,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

optional nit: not new but this as number cast is surprising.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I agree. I don't really understand why it's necessary, but it is.

Copy link
Copy Markdown
Contributor

@jacob314 jacob314 left a comment

Choose a reason for hiding this comment

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

lgtm

@jacob314 jacob314 disabled auto-merge November 20, 2025 19:43
@jacob314 jacob314 merged commit c7b5dcd into main Nov 20, 2025
75 of 88 checks passed
@jacob314 jacob314 deleted the tomm_compress branch November 20, 2025 19:43
@skeshive
Copy link
Copy Markdown
Contributor

/patch preview

@github-actions
Copy link
Copy Markdown

Patch workflow(s) dispatched successfully!

📋 Details:

  • Channels: preview
  • Commit: c7b5dcd28fe2b0f2cfa844c7f7c616f4f5657145
  • Workflows Created: 1

🔗 Track Progress:

@github-actions
Copy link
Copy Markdown

🚀 Patch PR Created!

📋 Patch Details:

📝 Next Steps:

  1. Review and approve the hotfix PR: #13529
  2. Once merged, the patch release will automatically trigger
  3. You'll receive updates here when the release completes

🔗 Track Progress:

@github-actions
Copy link
Copy Markdown

🚀 Patch Release Started!

📋 Release Details:

  • Environment: prod
  • Channel: preview → publishing to npm tag preview
  • Version: v0.17.0-preview.2
  • Hotfix PR: Merged ✅
  • Release Branch: release/v0.17.0-preview.2-pr-13517

⏳ Status: The patch release is now running. You'll receive another update when it completes.

🔗 Track Progress:

@github-actions
Copy link
Copy Markdown

Patch Release Complete!

📦 Release Details:

🎉 Status: Your patch has been successfully released and published to npm!

📝 What's Available:

🔗 Links:

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.

4 participants