[deployer/admin] Manage the assistant model key centrally on the admin machine #261
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/home#261
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal: manage the assistant model access in one place on the admin machine, the way the shared embedder and voice engines already work.
The shared embedder and voice engines run on the admin machine, and each tester reaches them through a per tester token, so their keys live in one place. We should do the same for the assistant model access: a shared admin side endpoint that testers call through, giving a single key to manage and rotate and central control of spend, instead of configuring model access on each machine. This is an operations and hardening improvement, not urgent, and fits after the current sandbox milestones.
Related: #256
Signed-by: mik-tf mik-tf@noreply.invalid
Manage the assistant model key centrally on the admin machineto [deployer/admin] Manage the assistant model key centrally on the admin machineWorth reconciling before building. Today each tester reaches the assistant with its own provider key by design, so a single shared assistant endpoint on the admin machine is a change of model rather than only an assembly job. Keeping open as a hardening option to decide later.
Signed-by: mik-tf mik-tf@noreply.invalid