Update .gitignore and configuration for model adjustments; refine query classification prompt

This commit is contained in:
Simone
2025-10-24 16:52:00 +02:00
parent 906b9c8520
commit 7098e05e44
3 changed files with 9 additions and 13 deletions

3
.gitignore vendored
View File

@@ -178,3 +178,6 @@ cython_debug/
# Gradio
.gradio/
# chat
chat.json

View File

@@ -40,7 +40,7 @@ api:
agents:
strategy: Conservative
team_model: qwen3:1.7b
team_model: qwen3:8b
team_leader_model: qwen3:8b
query_analyzer_model: qwen3:4b
report_generation_model: qwen3:8b
query_analyzer_model: qwen3:8b # query check
report_generation_model: qwen3:8b # ex predictor

View File

@@ -3,7 +3,7 @@
**CONTEXT:** Current date is {{CURRENT_DATE}}. You analyze user queries to determine if they can be processed by our crypto analysis system.
**CORE PRINCIPLE:** This is a **crypto-only application**. Resolve ambiguity in favor of cryptocurrency.
- Generic financial queries ("analyze the market", "give me a portfolio") classify as crypto
- Generic financial queries ("analyze the market", "give me a portfolio") will be classified as crypto
- Only reject queries that *explicitly* mention non-crypto assets
**CLASSIFICATION RULES:**
@@ -22,16 +22,9 @@
- Data requests without specifying which asset: "What's the price?", "Show me the volume"
- Examples: "What are the trends?", "Tell me the market cap"
**OUTPUT:** Respond with ONLY a valid JSON object (no markdown, no extra text):
**OUTPUT:** no markdown, no extra text
```json
{
"status": "IS_CRYPTO | NOT_CRYPTO | AMBIGUOUS",
"language": "en|it|es|...",
"reasoning": "Brief classification reason",
"response_message": "User message (empty for IS_CRYPTO)"
}
```
**RESPONSE MESSAGES:**
- `IS_CRYPTO`: `response_message` = `""`