Resolver modelos do Gemini e erros de execução#150
Open
rudnypc wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resumo
Este PR corrige a integração do SEI-Pro com os modelos mais recentes do Gemini e trata problemas de estabilidade que estavam quebrando a experiência no browser.
O que mudou
1. Suporte aos novos modelos Gemini
gemini-3.1-pro-previewgemini-3.1-flash-lite-previewv1beta, que é a versão compatível com esses modelos.2. Condensação para textos grandes
3. Correções de runtime e integração
checkHostLimit is not defined, adicionando uma proteção no bootstrap.seipro.appvia background/service worker, reduzindo bloqueios de CORS.manifestpara suportar o fluxo necessário no Chrome Extension Manifest V3.Benefícios
Testes realizados
node --checkmanifest.jsonv1betaObservações