You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ff18a4c
Browse filesBrowse the repository at this point in the historyBrowse files
fix: integrate ACP fixtures with current persona configuration
Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
Signed-off-by: Logan Johnson <[email protected]>
Copy file name to clipboardExpand all lines: desktop/src/features/agents/AGENTS.md
+22-22Lines changed: 22 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -308,6 +308,28 @@ with a TypeScript lookup table or an id comparison in a component.
308
308
309
309
17. **Databricks model discovery has one shared catalog authority.** Desktop and ACP call the shared `buzz-agent` discovery library; Desktop passes the effective merged `DATABRICKS_MODEL_FILTER` explicitly, and the library applies it to raw workspace endpoint IDs and Unity Catalog model-service FQNs after the additive union. A successful filtered-empty catalog is authoritative: it stays empty, disables switching, and never falls through to configured or known-model fallback. UC FQNs retain neutral effort capabilities. A boundary-matched GPT-5-or-newer family in the service-name component selects OpenAI Responses so tools can coexist with reasoning; other FQNs use MLflow Chat Completions. Catalog/schema components never influence routing. Keep this route-only rule identical in the Rust and TypeScript capability interpreters. Global Defaults preserves the discovered model ID as the selected value while its closed trigger renders the provider-scoped display label; do not force the raw persisted ID over that label.
310
310
311
+
18.**ACP transport is persona-owned before deployment.** Select `acp_command` in the persona create/edit form beside the harness. Deployment inherits that value; linked instances do not expose a competing post-deploy override. Legacy definitions without the field use `buzz-acp`; definition-less agents retain their stored command. Switching a linked definition back to stock resets the instance transport on the next spawn. Shared persona events and restart snapshots carry the field so edits apply on the next spawn.
312
+
313
+
19.**ACP command selection is convention-based.** The editor always offers
314
+
stock `buzz-acp` and installed executable `buzz-*-acp` aliases discovered
315
+
from normal executable search directories. It does not offer arbitrary
316
+
command entry. A persisted value outside that set remains visible as an
317
+
unavailable compatibility option but is not editable; selecting a conventional
318
+
option replaces it. Discovery returns the path produced by the same resolver
319
+
used at spawn, so a duplicate alias must never advertise one executable and
320
+
later launch another. Keep these transitions in the pure
321
+
`ui/acpCommandPicker.ts` helper and preserve persisted values across loading,
322
+
failed discovery, and late candidate arrival. ACP-only selections must mark
323
+
the form dirty, including catalog-update and embedded discard protection.
324
+
Catalog and portable agent/team snapshots carry only stock or conventional
325
+
aliases (ASCII letters, digits, hyphens, and underscores in the middle).
326
+
Foreign artifacts with other command values are rejected; exports omit
327
+
legacy machine-local commands. Owner-native and owner-device synchronization
328
+
retain custom-command compatibility and are not an execution sandbox.
329
+
Shared persona heads redact nonportable commands and emit explicit stock
330
+
for resets; owner replay of a redacted head preserves only a nonportable
331
+
local override. That local path is not synchronized through catalog heads.
332
+
311
333
## Channel-only runtime controls
312
334
313
335
Desktop observer controls identify a channel, not a thread session. The harness
16.**ACP transport is persona-owned before deployment.** Select `acp_command` in the persona create/edit form beside the harness. Deployment inherits that value; linked instances do not expose a competing post-deploy override. Legacy definitions without the field use `buzz-acp`; definition-less agents retain their stored command. Switching a linked definition back to stock resets the instance transport on the next spawn. Shared persona events and restart snapshots carry the field so edits apply on the next spawn.
337
-
338
-
17.**ACP command selection is convention-based.** The editor always offers
339
-
stock `buzz-acp` and installed executable `buzz-*-acp` aliases discovered
340
-
from normal executable search directories. It does not offer arbitrary
341
-
command entry. A persisted value outside that set remains visible as an
342
-
unavailable compatibility option but is not editable; selecting a conventional
343
-
option replaces it. Discovery returns the path produced by the same resolver
344
-
used at spawn, so a duplicate alias must never advertise one executable and
345
-
later launch another. Keep these transitions in the pure
346
-
`ui/acpCommandPicker.ts` helper and preserve persisted values across loading,
347
-
failed discovery, and late candidate arrival. ACP-only selections must mark
348
-
the form dirty, including catalog-update and embedded discard protection.
349
-
Catalog and portable agent/team snapshots carry only stock or conventional
350
-
aliases (ASCII letters, digits, hyphens, and underscores in the middle).
351
-
Foreign artifacts with other command values are rejected; exports omit
352
-
legacy machine-local commands. Owner-native and owner-device synchronization
353
-
retain custom-command compatibility and are not an execution sandbox.
354
-
Shared persona heads redact nonportable commands and emit explicit stock
355
-
for resets; owner replay of a redacted head preserves only a nonportable
356
-
local override. That local path is not synchronized through catalog heads.
357
-
358
358
## The tests that enforce this
359
359
360
360
-`lib/agentConfigCore.test.mjs` — field model per harness × scope, clearing
0 commit comments