[ENHANCEMENT]: Centralize Groq model configuration instead of hardcoding model IDs across backend modules
@subhamoydatta703 ci sta già lavorando.
Dal 9/10/2026.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 52/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- python, typescript
- Ambito
- backend, documentation, frontend
Direzione di ricerca
Start with the six backend modules listed under Affected locations and inspect how their model IDs are passed to the Groq calls. Then read backend/.env.example, frontend/app/[locale]/analyze/results/page.tsx, and AGENTS.md to resolve the model source of truth. Done means the models are centrally configurable, existing defaults remain unchanged, and the backend, UI, and documentation agree.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Feature and its Use Cases
Summary
The Groq model IDs are hardcoded as string literals in six backend modules. Changing or replacing a model (for example if Groq deprecates one, or to compare cost and quality) requires editing every file, and the choice of model per task is not documented in one place.
Affected locations
backend/app/modules/langgraph_nodes/sentiment.py(line 52)backend/app/modules/langgraph_nodes/judge.py(line 38)backend/app/modules/langgraph_nodes/generate_perspective.py(line 25)backend/app/modules/facts_check/llm_processing.py(lines 66 and 131)backend/app/modules/bias_detection/check_bias.py(line 66)backend/app/modules/chat/llm_processing.py(line 58)
Problem
- Model IDs are duplicated across multiple files, so they can drift apart and are easy to miss when one changes.
- There is no single place to see or change which model each task uses.
- The results screen labels the judge as "Groq LLaMA 3.3" (
frontend/app/[locale]/analyze/results/page.tsx, line 319) andAGENTS.mdspecifies "Groq SDK (LLaMA 3.3)", while the backend code uses different model IDs. The documentation, UI and code are therefore inconsistent.
Proposed solution
- Add a small shared configuration module that defines the models used for complex generation and for fast classification.
- Allow overriding them through environment variables (for example
GROQ_MODELandGROQ_FAST_MODEL), documented inbackend/.env.example. - Replace the hardcoded strings in the six modules with the shared configuration.
- Keep the models currently used in the code as the defaults, so this change does not alter runtime behavior unless a deployer sets the variables.
- Make the UI label, documentation and
AGENTS.mdconsistent with the configured models.
Question for maintainers
The code, the results screen and AGENTS.md currently disagree about which model is used. Which should be the source of truth: the models in the code today, or the LLaMA 3.3 models named in the documentation and UI? I'd like to align with your preference before implementing.
Benefits
Simpler model upgrades or replacements, easier cost and quality tuning, and fewer inconsistencies.
Environment
- Branch / commit:
mainat70a2af4d9e98e659d1bc0bdf0d8551f91dee0638
Additional Context
Additional Context
Visual Reference
The "Tone & Reliability" card on the analysis results page displays "Model Judge: Groq LLaMA 3.3".
Inconsistency Between UI, Documentation and Code
- Results UI: the card shows "Model Judge: Groq LLaMA 3.3" (
frontend/app/[locale]/analyze/results/page.tsx, lines 318-320). - Documentation:
AGENTS.mdlists the stack as "Groq SDK (LLaMA 3.3)". - Backend code: the LLM calls use different model IDs:
openai/gpt-oss-20binjudge.pyandsentiment.pyopenai/gpt-oss-120bingenerate_perspective.py,check_bias.pyandchat/llm_processing.py
The UI and documentation therefore name a different model from the one used by the backend. Centralizing the model configuration would make it possible to keep all three consistent.
Code of Conduct
- I have joined the Discord server and will post updates there
- I have searched existing issues to avoid duplicates
- Lingua principale
- TypeScript
- Stelle
- 58
- Fork
- 90
- Merge medio
- 11h 51m
- PR unite (30g)
- 3
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di AOSSIE-Org/Perspective
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
AOSSIE-Org/Perspective#191 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
AOSSIE-Org/Perspective#190 ·
-
[BUG]: Missing input validation in URlRequest and ChatQuery causes 500 crashes and wasteful scraper executionForse già presa @agarwalpranav0711 l’ha presa 25 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
AOSSIE-Org/Perspective#178 ·
-
[BUG]: chunk_rag_data crashes with ValueError when perspective is a dict, silently dropping RAG vector storageForse già presa @agarwalpranav0711 l’ha presa 36 giorni fa. Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
AOSSIE-Org/Perspective#175 ·
-
[BUG]: Scraper passes headers as query params in requests.get (User-Agent never sent)Forse già presa @Th-Shivam l’ha presa 50 giorni fa. Apertabug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
AOSSIE-Org/Perspective#161 · 1 commento ·
Tutte le issue di AOSSIE-Org/Perspective
Issue simili
-
documentation lens:human needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
thebristolsound/birdbrain#2246 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
A voting window past about 69.9 million hours stores a deadline that reads back as no deadlineApertabug ready-for-human
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
BoardGamesEmpire/board-games-empire-backend#1452 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
good first issue stretch
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno