Files
buzz/desktop/src
npub1223z34hd7vtwc6qj4s7flsxkj644nlre2nthu7lrrmkumhu3xddsrx9r6w b6519f5f0e fix(agents): carry the backend provider into persona templates
Corrects an earlier call to omit provider from the save-as-persona-template
port. On main the provider is NOT a top-level ManagedAgent field, but it is
NOT absent either — it lives in the backend union: a `{ type: "provider",
id }` backend carries the provider id, while a `{ type: "local" }` backend
has none.

- saveAsPersonaTemplateDialogState now derives provider from agent.backend
  (providerForAgentBackend): a provider backend carries backend.id; a local
  backend leaves it unset. A databricks agent promotes with its provider
  instead of losing it.
- CreateAgentDialog's opt-in template mint mirrors this: it carries the
  selected backend provider (runOn) when the agent runs on a provider.

Tests updated: provider carries from a provider backend; stays unset for a
local backend.

Co-authored-by: Taylor Ho <taylorkmho@gmail.com>
Signed-off-by: Taylor Ho <taylorkmho@gmail.com>
2026-06-26 13:59:38 -07:00
..
2026-03-09 13:02:11 -07:00