You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: config/settings.json
+58-2Lines changed: 58 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,16 @@
17
17
"chunk_overlap": 40,
18
18
"max_chunk_length": 512,
19
19
"semantic_word_limit": 1024,
20
-
"top_k": 3
20
+
"top_k": 3,
21
+
"rerank": {
22
+
"enabled": true,
23
+
"provider": "local_oss",
24
+
"model": "",
25
+
"candidate_k": 40,
26
+
"top_k": null,
27
+
"timeout_seconds": 8.0,
28
+
"batch_size": 8
29
+
}
21
30
},
22
31
"agent": {
23
32
"model_provider": "ollama",
@@ -44,7 +53,54 @@
44
53
"test_agent_model": "gemma3:4b"
45
54
},
46
55
"remme": {
47
-
"extraction_prompt": "You are a Contextual Memory Management AI.\nYour job is to update the \"Memory Vault\" based on the latest conversation.\n\nRULES:\n1. ANTI-FRAGMENTATION: NEVER split related items into separate facts. Merge them into ONE rich, coherent memory entry.\n2. NO REDUNDANCY: If info is already captured, do nothing unless you have NEW details (use \"update\").\n3. CONTEXTUAL HUBS: Prefer a single \"Hub\" memory over separate atomic facts; emit it as one entry in \"memories\" (see OUTPUT FORMAT).\n4. NO NEGATIVE FACTS: NEVER store \"not found\" or \"missing\" info.\n5. NO META-LOGS: Do not store internal reasoning or agent traces.\n6. HIGH SALIENCE ONLY: Focus on project decisions, user preferences, architectural details.\n7. ACTIONS: \"add\" for new facts, \"update\" to expand existing, \"delete\" if proven false.\n\nOUTPUT FORMAT: Respond with JSON only: {\"memories\": [{\"action\": \"add\"|\"update\"|\"delete\", \"text\": \"...\", \"id\": \"...\" only for update/delete}], \"preferences\": {...}}. If nothing to store: {\"memories\": [], \"preferences\": {}}."
56
+
"extraction_prompt": "You are a Contextual Memory Management AI.\nYour job is to update the \"Memory Vault\" based on the latest conversation.\n\nRULES:\n1. ANTI-FRAGMENTATION: NEVER split related items into separate facts. Merge them into ONE rich, coherent memory entry.\n2. NO REDUNDANCY: If info is already captured, do nothing unless you have NEW details (use \"update\").\n3. CONTEXTUAL HUBS: Prefer a single \"Hub\" memory over separate atomic facts; emit it as one entry in \"memories\" (see OUTPUT FORMAT).\n4. NO NEGATIVE FACTS: NEVER store \"not found\" or \"missing\" info.\n5. NO META-LOGS: Do not store internal reasoning or agent traces.\n6. HIGH SALIENCE ONLY: Focus on project decisions, user preferences, architectural details.\n7. ACTIONS: \"add\" for new facts, \"update\" to expand existing, \"delete\" if proven false.\n\nOUTPUT FORMAT: Respond with JSON only: {\"memories\": [{\"action\": \"add\"|\"update\"|\"delete\", \"text\": \"...\", \"id\": \"...\" only for update/delete}], \"preferences\": {...}}. If nothing to store: {\"memories\": [], \"preferences\": {}}.",
0 commit comments