Buddy's surface shows T3's model and effort picker under the composer #123

Activity

1. immakermatty commented on Oct 25, 2026

   

   immakermatty

   on Oct 25, 2026

   Last edited by immakermatty

   Author

   More actions

   The picker isn't only shown: it sets Buddy's model. That collides with Buddy's profiles (root 0210, addendum of 2026-10-20/21, point 9: the person switches profiles in Nastavení → Buddy and doesn't tune single values).

   How it works today (read on main of both forks, 2026-10-25):

   • Lazurio/hermes-agent's overlay row acp: model and thought_level session config options on the gateway viewer (2026-10-22, acp_adapter/lazurio_config_options.py) advertises model and thought_level as session config options. Setting one runs the session's model pick or its /reasoning level.
   • T3's ACP adapter (packages/provider-acp/src/server/adapter.ts, configureSession) applies the thread's stored modelSelection:
     • at session start;
     • at every session activation, for example after an interrupt or a T3 restart;
     • whenever the selection changes.
       It runs setConfigOption for the model, then for each option.
   • So each session T3 activates for Buddy's thread gets T3's stored choice (today gpt-6.1-sol, high), whatever Hermes is configured with.

   Today the stored choice equals the default profile Důkladný, so nothing visible happens. Once Nastavení → Buddy switches profiles (LazurioPlatform, plan DEV-6676), a switch to another profile would be undone in the web chat at the next session activation.

   So the fix has two parts:

   1. Buddy's surface draws no model or effort control (this issue as filed).
   2. T3 sends Buddy's sessions no model or option selection, so Hermes's own configuration decides, which is the one the profile writes.
      • The provider instance would declare that its agent owns the model, and configureSession would skip the selection for it.
      • The Hermes overlay row would then have no Lazurio consumer that I know of, and could go at the next stable refresh (to be checked then).

   Part 2 is the contract, and it belongs with the profile switch. Its test is on a real Buddy: a profile switch survives a session activation from the web chat. Part 1 can ship alone. On its own it only hides a control that still decides the model.