mara/hyperhive
mara/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

swarm-ui: set the review classifier's keys from the classifier settings

Browse source 
The classifier's Anthropic and ACP provider keys were written by hand in the
secret store's UI. The controller now stores them: GET
/api/review-classifier/keys says whether each is set and when it changed, and
PUT /api/review-classifier/keys/{runtime} writes one. No route answers a key.

The controller's store policy gains create and update on the two leaves with
no read of their values, and a metadata read for the set state. The swarm UI's
classifier settings card gets a key form beside the settings, saved apart
because it goes to the secret store.
This commit is contained in:
iris 2026-11-11 18:29:29 +01:00 • committed by mara
commit 6875a4f0f8
1 changed files with 628 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/4-implementation/web-ui/swarm-ui.md
View file

@ -327,8 +327,15 @@ limit gets a no-verdict review, and a try-out with more gets a 400.
the runtime, model, effort and limits, and the provider too while the runtime is
ACP, so switching back to API key keeps the stored provider for next time. If
the controller refuses it, the page shows the reason and leaves the form as you
typed it. A change takes effect from the next run, with no restart. The page
has no API key field: admins set each runtime's key in the bao UI.
typed it. A change takes effect from the next run, with no restart.
Under the settings form sits a **key** form for the runtime the form chooses.
Its label says whether that runtime has a key and when it last changed
(`GET /api/review-classifier/keys`, which never answers a key). The field is a
password input; **save key** sends it alone with `PUT
/api/review-classifier/keys/{runtime}`, apart from the settings, and clears the
field once the controller has stored it. Switching the runtime drops a key you
typed for the other one.
### Scheduled prompts