Switch the extract and summarise stages on the page, over config.yaml

A stored `stage:extract` / `stage:summarise` in the state table overrides
extract.enabled / summarise.enabled; with none, the file applies. One
function, stages.stage_on, decides, and both tasks' finders ask it.
GET/PUT /api/stages and `app stages` show and set it with who would answer;
Runs has a "What the model reads" block, and a search agent's card says when
a stage is off and links to the switch.

Co-Authored-By: Claude Sonnet <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Sonnet committed 2026-09-29 15:54:53 +02:00
1 parent a629eda8de
commit 471ace703c
15 files changed
+593 -23

No files matched your search

+6 -2
View File
@@ -51,7 +51,9 @@ agent:
# default: on the API backend every batch of 20 roles is a paid call. On, a
# pull reads only the best roles of every enabled agent, as deep and as low
# as that agent's own limits say (see agents below), after a first score; a
# second score then applies the gates to what was filled.
# second score then applies the gates to what was filled. `enabled` is only the
# default for a fresh database: the switch under Settings, Sources, Runs (or
# `app stages extract on|off`) overrides it and needs no restart.
extract:
enabled: false
model: claude-haiku-4-5-20251001
@@ -60,7 +62,9 @@ extract:
# (app/jobs/summarise.py). Off by default. On, each pull summarises the best
# roles of every enabled agent that have none yet, by that agent's limits, so
# the cost stays bounded however many roles are open. The Summarise button on
# a role's page asks for that one role either way.
# a role's page asks for that one role either way. `enabled` is only the
# default for a fresh database: the switch under Settings, Sources, Runs (or
# `app stages summarise on|off`) overrides it and needs no restart.
summarise:
enabled: false
model: claude-haiku-4-5-20251001