Extract and summarise bounds are each agent's own limits, set on its form
agents.limits holds extract_top, extract_min, summarise_top and summarise_min; the scope query reads them per ranked row, and a row saved before this behaves like a fresh agent. The four global config keys go. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
1 parent
e602eb3388
commit
cebe62ddc9
20 files changed
+229
-147
No files matched your search
+3
-6
@@ -17,20 +17,17 @@ workers:
|
||||
extract:
|
||||
enabled: false
|
||||
model: claude-haiku-4-5-20251001
|
||||
per_agent: 500
|
||||
min_score: 0.3
|
||||
summarise:
|
||||
enabled: false
|
||||
model: claude-haiku-4-5-20251001
|
||||
per_agent: 30
|
||||
min_score: 0.5
|
||||
embed:
|
||||
model: sentence-transformers/all-MiniLM-L6-v2
|
||||
sources: {}
|
||||
# The starter ranking, imported once into an empty table. Edit it under
|
||||
# Settings, Ranking afterwards; this list is not read again. EU in a country
|
||||
# gate is a role open anywhere in Europe ("Remote - Europe", "EMEA"). Two more
|
||||
# are in config.example.yaml.
|
||||
# gate is a role open anywhere in Europe ("Remote - Europe", "EMEA"). How deep
|
||||
# into the ranking extract and summarise read is each agent's `limits`, see
|
||||
# config.example.yaml, which has two more agents.
|
||||
agents:
|
||||
- name: Copenhagen engineering
|
||||
intent: >-
|
||||
|
||||
Reference in new issue
Block a user